Project Management System
NIC
A Project Report On
PROJECT MANAGEMENT SYSTEM Developed For National Informatics Centre (NIC) New Delhi
Submitted towards partial fulfillment for the award of the degree of
MASTER OF COMPUTER APPLICATION
2002-2006 Submitted By Santosh Kumar Singh Enrollment No:02/41132 Under the guidance of External Guide: Mr. Pradeep Singh AG Scientific Officer Integrated Finance Division National Informatics Centre Internal Guide: Mr. B.D Choudhary Associate Professor Department of Computer Science Apex Institute Of Management and Sciences
Department of Computer Science APEX INSTITUTE OF MANAGEMENT AND SCIENCES JAIPUR (RAJ)
(Affiliated to Rajasthan University, Jaipur)
1
Project Management System
NIC
CERTIFICATE
This is to certify that Mr. Santosh Kumar Singh , ID.N0. 7847, a student of M.C.A. from Apex Institute Of Management And Sciences, Jaipur affiliated to Rajasthan University Jaipur has done his full-semester project training for the batch September, 2005 at Integrated Finance Division, NIC, CGO Complex, New Delhi. The project work entitled ―Project Management System‖ embodies the original work done by Mr. Santosh Kumar Singh during his full semester project-training period.
(Mr. Pradeep Singh AG) Scientific Officer Integrated Finance Division National Informatics Centre New Delhi-110003
(Mr. R.K.Saini) Joint Director / AFA Integrated Finance Division National Informatics Centre New Delhi-110003
Department of Computer Science Apex Institute of Management and Sciences
Jaipur (Rajasthan) 2
Project Management System
NIC
CERTIFICATE
This is to certify that the project entitled Project Management System has been designed and developed by Santosh Kumar Singh in partial fulfillment of the degree of MCA 2006 Examination, under our supervision and guidance.
Mr. B.D Choudhary H.O.D. Department of Computer Science Apex Institute Of Management And Sciences ,Jaipur
Dr.J.M Ovasdi Principal Apex Institute Of Management And Sciences ,Jaipur
3
Project Management System
NIC CANDIDATE’S DECELERATION
I here by declare that I Santosh Kumar Singh Candidate I.D.No-7847 Student of Apex Institute Of Management and Sciences Jaipur Affiliated To Unversity Of Rajasthan .I have done my Six month project training at NIC Delhi in the Integrated finance Division Form 23/9/2005 to 23/03/2006 .Under the guidance of Mr Pradeep Singh AG.Scientific officer at the Integrated finance Division. Project Title is ―Project Management System‖ in Visual Studio.NET in ASP.NET Though C#. According to me each and every information is correct .
Santosh Kumar Singh MCA (VI Sem) Apex Institute of Management And Sciences Jaipur (Rajasthan).
4
Project Management System
NIC
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 acknowledge the effort of those who have contributed significantly to my project. I express my sincere gratitude and thankfulness towards Mr. B.D Choudhary,(H.O.D) at Department of Computer Science, Apex Institue of Management And Sciences ,Jaipur affiliated to Rajasthan University for their valuable time and guidance throughout the MCA. I feel privileged to offer my sincere thanks and deep sense of gratitude to Mr. Pradeep Singh AG, Scientific Officer at Integrated Finance Division , NIC, for expressing his confidence in me by letting me work on a project of this magnitude and using latest technologies and providing her support, help & encouragement in implementing this project. I am grateful for the co-operation & valuable suggestions rendered by Mr R..K.Saini, Assistant Financial Advisor & Head of Integrated Finance Division and all the staff members of the National Informatics Centre, New Delhi. I am grateful to all our friends for providing critical feedback & support whenever required. There are times in such projects when the clock beats you time & again & you run out of energy, you just want to finish it once & forever. Parents made us endure such times with their unfailing humour & warm wishes. I regret any inadvertent omissions.
Santosh Kumar Singh MCA (VI Sem) Apex Institute of Management And Sciences Jaipur (Rajasthan).
5
Project Management System
NIC ABSTRACT
This project report provides an elaborate coverage of the salient features of developing software, its capabilities, and its limitations and of course all software development process followed. The project has been developed to fulfill the requirements of the Integrated Finances Systems. The current product is a part of overall web-based Finance need of the Department. The tools used in this the ASP.NET And C#.NET .
6
Project Management System
NIC
Table of Contents
1.
Introduction o About NIC ……………………………………………………… 1 o Project Description …………………………………………….14 o System Requirements ………………………………………...15 o Tools & Technology Used …………………………………….16
2. System Analysis o Information Gathering……………………………………… . 42 o Existing System ………………………………………………. 42 o Proposed System ……………………………………………… 43 o Feasibility Study ………………………………………………. 43 3. System Design o Data Flow Diagrams ……………………………………………45 o Database Design ……………………………………………….. 46 o Screenshots ……………………………………………………..62 4. Conclusion ……………………………………………………………………71 5. Bibliography ………………………………………………………………….72 Technical Feasibility ………………………………….. 43 Economical Feasibility ………………………………... 44 Operational Feasibility ………………………………. 44
7
Project Management System
NIC
Introduction
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 decentralised 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 endeavours 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 Centres 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 conceptualised, developed and implemented a very large number of projects for various Central and State Government Ministries, Departments and Organisations. Many of these
8
Project Management System
NIC
projects are continuing projects being carried out by various divisions of NIC at New Delhi Headquarters and State/District centres 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 e-governance and thereby influencing the lives of millions of citizens of India are given below:
2. Agricultural Marketing Information Network (AGMARKNET) 3. Central Passport System 4. Community Information Centres (CICs) 5. Computerised Rural Information Systems Project (CRISP) 6. Court Information System (COURTIS) 7. Department of Agriculture Network (DACNET) 8. Examination Results Portal 9. India Image 10. Land Records Information System (LRIS) 11. National Hazardous Waste Information System (NHWIS) 12. Public Grievance Redress and Monitoring System (PGRAMS) 13. Spatial Data Infrastructure (SDI) 14. Training
9
Project Management System
NIC
15. Video Conferencing Web Site of NIC: http://indiaimage.nic.in/
State/UT units: 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 Infomatics Offices.
Contact Details of NICs State Units Andaman & Nicobar(UT) Haryana Nagaland C/O Development Commissioner Kohima-795001 Nagaland E-mail :sionga@hub.nic.in Orissa Unit-IV Sachivalaya Marg Bhubaneshwar751001 Orissa E-mail :sio@ori.nic.in
Room No.G03 Old DAB Building Ground Floor Admin Secretariat New Secretariat Building Port Blair-744101 Sector-17 Andaman & Nicobar Chandigarh-160017 E-mail Haryana :andaman@hub.nic.in E-Mail:sio@hry.nic.in Andhra Pradesh Himachal Pradesh NIC - A-Block 6th Floor Armsdale Govt. Offices Building Complex Chhota Shimla Tank Bund Road Shimla-171002 Hyderabad-500029 Himachal Pradesh Andhra Pradesh E-mail : sio@hp.nic.in E-mail :sio@ap.nic.in Arunachal Pradesh Jammu and Kashmir Block-23, Secretariat Room No. NB-12 Itanagar - 791111 Mini Secretariat Bldg Arunachal Pradesh Jammu-180001 E-mail : sioJammu & Kashmir arn@hub.nic.in Email: sio@jk.nic.in Assam Jharkhand Block F, Secretariat Complex Dispur Guwahati-781006 Assam E-mail :sioasm@hub.nic.in Bihar 3rd Floor,
Pondicherry (UT) 4th Floor Chief Secretariat Pondicherry-605001 E-mail :sio@pondy.pon.nic.in Punjab Room No. 109, 104/3, Nepal House Ground Floor, Doranda, Ranchi - 834 Punjab Mini 002 Secretariat, Sector-9 Email: sioChandigarh-160009. jhr@hub.nic.in Punjab E-mail :punjab@chd.nic.in Karnataka Rajasthan 6 & 7th Floor, Mini 318, North- West
10
Project Management System
NIC
Technology Bhawan Tower Beilly Road Dr. Ambedkar Road Patna-800015 Bangalore-560001 Bihar Karnataka E-mail E-mail : :sio@bsu.bih.nic.in sio@ksu.kar.nic.in Chandigarh (UT) Kerala NIC Chandigarh UT Unit ER & DC Building 222, 2nd floor, UT Keltron House Secretariat Thiruvananthapuram Sector 9-D, 695033 Chandigarh-160017 Kerala EEmail: sio@kerala.nic.in mail:sio@chdut.nic.in Chhattisgarh Lakshadweep (UT) Room No. 238, Territory Unit Mantralaya Union Territory of (D.K.Bhawan) Lakshdweep Island Raipur Kavaratti-682555 Chhattisgarh E-mail :sioE-mail : siolaks@hub.nic.in cg@hub.nic.in Dadra and Nagar Madhya Pradesh Haveli (UT) C/o. Collectorate Office Silvassa, Dadra & Nagar Haveli E-mail : siodadra@hub.nic.in Daman and Diu (UT) Secretariat, Ist Floor Fort Area Moti Daman-396 220 Daman & Diu E-mail :daman@guj.nic.in Delhi Computer Centre 'C' Wing, Basement Vindhyachal Bhavan Bhopal-462004 Madhya Pradesh Email:sio@mp.nic.in Maharashtra 11th Floor, New Administrative Bldg. Opp. Mantralaya Madam Cama Road Mumbai-400032 Maharastra E-mail :siomsu@hub.nic.in Manipur Block Govt. Secretariat Jaipur-302005 Rajasthan Email :sio@raj.nic.in Sikkim Tashiling Secretariate Gangtok- 737103 Sikkim E-mail : siosik@hub.nic.in Tamil Nadu E-2-A, Rajaji Bhavan Besant Nagar Chennai - 600 090 Tamil Nadu E-mail : sio@tn.nic.in Tripura Treasury No. 2nd Floor Secretariat Complex Agartala-799001 Tripura E-mail :siotrpr@hub.nic.in Uttar Pradesh 6th Floor, Yojana Bhavan 9 Sarojini Naidu Marg Lucknow - 226001 Uttar Pradesh E-mail : upstate@up.nic.in Uttaranchal NIC, State Unit Uttaranchal C/o. District Computer Centre Room No. 18, Collectorate Dehradun -248001 Uttaranchal E- mail : utrnchal@up.nic.in
Room No 79 New Secretariat Level - 3, B-Wing Ministers' Block Delhi Sachivalaya Imphal - 795001 Delhi-110054 Manipur E-mail : email address : sioskapoor@hub.nic.in man@hub.nic.in & manipur@msu.man.nic.in
11
Project Management System
NIC
Meghalaya West Bengal Computer Cell Ground Floor Paraiso de Goa Room No. 10 Bidyut Bhavan H- Block, Porvorim Additional Secretariat D.J. Block Sector II Bardez - 403 521 Shillong-793001 Salt Lake Goa Meghalaya Kolkata-700091 Ph 0832-2415545 E-mail :sioWest Bengal E-mail : megh@hub.nic.in E-mail sio@goa.nic.in sio@shillong.meg.nic.in :sio@wbsu.wb.nic.in Gujarat Mizoram Secretariat Complex , Block No. 13, Second Block - C Floor Room No. C-10, New Sachivalaya Treasury Square Gandhinagar-382010 Aizawal-796001 Gujarat Mizoram E-mail : E-mail : siosio@guj.nic.in mizo@hub.nic. Goa
District Units:-
At the District level, NIC District Centres provide effective informatics support to the Development, Revenue and Judiciary administration of the District.
NIC District Centres
Andaman and Nicobar Haryana Nagaland (UT) Andhra Pradesh Himachal Pradesh Orissa Jammu and Pondicherry Arunachal Pradesh Kashmir (UT) Assam Jharkhand Punjab Bihar Karnataka Rajasthan Chandigarh (UT) Kerala Sikkim Lakshadweep Chhattisgarh Tamil Nadu (UT) Dadra and Nagar Haveli Madhya Pradesh Tripura (UT) Daman and Diu (UT) Maharashtra Uttar Pradesh Delhi (UT) Manipur Uttaranchal Goa Meghalaya West Bengal Gujarat Mizoram
12
Project Management System
NIC
History: -
Computers were used on a large scale for the first time during the World War II for military data processing. Its non-military uses gained momentum in the post-war period. India was one of the first countries of the world to utilise the capability of computers in Education, R&D, Planning and National Development. The developments during ‘50s and ’60s in terms of computer resources chronicled here would testify to this trend.
Arrival of Computers in India
1950 1954
First Analog Computer at the Indian Statistical Institute (ISI), Kolkata
First digital computer – HEC-2M developed by A.D. Booth at Birbeek College, London for ISI.
HEC-2M operational at ISI in August URAL from the Soviet Union through the United Nation‘s Technical Assistance for ISI. First commercial computer installed by ESSO Standard Eastern Inc., Bombay (Mumbai) 14 computers in R&D organisation IBM 1620 at IIT, Kanpur IBM 1401 by IBM for ISI to supplant the above two CDC 3600 acquired by TIFR, Mumbai 30 commercial installations IBM 7044 at IIT, Kanpur 10 Honeywell Computers at Department of Statistics, Cabinet Secretariat IBM 1401 at IIT, Kanpur IBM computer at Planning Commission under a grant of Ford Foundation
1955 1958 1961 1962-1964 1963 1964 1965 1965-1966 1966 1967 1968 1969
13
Project Management System
NIC
Number of Computers in India as on 1 August 1974
Year 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1971-‘74* Total
No. of Computers Installed 2 1 2 8 12 16 22 20 21 11 33 14 16 11 28 217
1971-‘74* - Exact year of installations not known but installed during this period. Source: Two Hundred and Twenty First Report of the Public Accounts Committee (1975-76) on Computerisation in Government Departments. Department of Electronics. p3,1976, Lok Sabha Secretariat, New Delhi.
14
Project Management System
NIC
Government of India Initiatives
After the war with China in 1962, the Governemnt of India realised the importance and felt the need of a strong indigenous electronics base for security and national development and accordingly set up the Electronics Committee (also known as the Bhabha Committee) under the Chairmanship of the renowned nuclear scientist Dr. Homi J Bhabha. The Committee in its report in 1966 focussed on computers as tools ―to the development of a new outlook and a new scientific culture‖ and suggested the establishment of a National Computer Centre and five regional centres. The Electronics Committee convened a National Conference on Electronics in 1968 wherein Dr. Vikram Sarabhai, the then Chairman of the Committee, suggested the formation of National Informatics Organisation towards fulfilling the goal of a self-reliant electronics industry. Recognising the need for rapid progress in this regard, the Government of India set up a separate Department of Electronics (DOE) with effect from 26th June 1970 with Professor M.G.K. Menon as the Secretary of the Department. The department functioned directly under Prime Minister as a scientific department. The Government constituted the Electronics Commission in February 1971 under the Chairmanship of Professor M.G.K. Menon. For policy formulation and implementation through meaningful, effective and in-depth studies in the field of electronics including computer industry, an Information, Planning and Analysis Group (IPAG) of the Electronics Commission was constituted in October 1971 with Dr. N. Seshagiri as its Director. The Headquarters of the Department of Electronics were at Delhi and those of the Electronics Commission at Mumbai (then Bombay).
15
Project Management System
NIC
The IPAG as part of the Electronics Commission was centred at Mumbai.
GENESIS The Electronics Commission and the DOE put forward a proposal to UNDP for assistance to set up a National Computer Centre in Delhi for building up national data bases, developing the methodologies for utilising these, and for defining the various options and paths in decision-making at the national level. A UNDP team visited Delhi in March 1975 to study the proposal. The UNDP agreed to fund the National Informatics Centre to the extent of US $4.4 million for the purchase of a large computer system (costing approximately US $3.3 million), other hardware, training, the services of experts, etc. The 1976-‘77 Annual Report of the DOE noted: ‗In view of this, action has been taken to proceed with the preliminary work relating to the National Informatics Centre so that when UNDP financial assistance becomes available and the major hardware is commissioned (in 1978 on the basis of current information), the Centre can get on with its work on an
expeditious basis. NIC is a plan project administered by the Information, Planning and Analysis Group (IPAG) of the Electronics Commission in its initial stages‘. The Advisory Council set up for the NIC in 1976-1977 had the following composition:
1. 2. 3. 4. 5. Prof. M. G. K. Menon, Chairman, Electronics Commission Chairman Shri M. Satyapal, Advisor (I&M), Planning Commission Member Shri C.S. Swaminathan, Controller General of Accounts, Member Ministry of Finance Prof. V. S. Rajamani, Professor, Indian Institute of Member Technology, Delhi Col. A. Balasubramanian, Officer on Special Duty, Member Department of Electronics
16
Project Management System
NIC
6. Dr. N. Seshagiri, Director (IPAG) and Executive Director Member (Protem), NIC
Objective: -
The long-term objective of the National Informatics Centre, as approved by the Planning Commission, Ministry of Finance and the Electronics Commission, is ‘to establish the feasibility of a system for the provision of detailed information to government ministries and agencies to assist them in making decisions relating to the country’s economic and social development planning and programme implementation’. (Annual Report of the Department of Electronics, Government of India, 1977-’78,p172.)
NIC was set up with the objective to promote economic, social, scientific and technological activities, and also for macro-economic adjustment programme of the Government, through the applications of IT.
17
Project Management System
NIC
Mandate: -
As laid down in the Annual Reports of DOE 1976-'77 and 1977-'78, NIC was given the mandate to
Provide this informatics service to various user agencies in Government
Play a promotional role in creating appropriate information systems in Government
Act as a focal point for developing, managing and operating information system in Government
Act as a focal point for development of methodologies for designing and implementing national information systems and data
management techniques Act as a focal point for maintaining inventories of primary data and computer-based systems for data collection and dissemination Train users in information systems, data management and computing techniques
18
Project Management System
NIC
Ten information systems were planned for development by NIC in the following sectors:
Agriculture Construction and Transport Education and Manpower Energy Finance Industry Small-Scale Industries Socio-Economic Index Trade and Media Government Archival Information
With this, NIC embarked on a grandiose mission to develop various national databases for use in planning and decision making by the government.
19
Project Management System
NIC
Evolution: -
Starting as a small programme under an external stimulus by an UNDP project in early 1970s, NIC started functioning in 1977 and since then it has grown incrementally and later exponentially as one of India’s major S&T Organisations promoting Informatics-led Development, which has helped to usher in the required transformation to cope with the trends in the new millenium.
NIC has played an important role of an active catalyst and facilitator in informatics development programme in Governments at the national, state and district levels, during the last 26 years which made them take policy decisions to create knowledge societies – societies that can exploit knowledge to derive competitive advantage using the opportunities provided by digital technology. NIC has been instrumental in adopting Information Technology and Communication Technology to reach out into India i.e. by implementing IT applications in Social and Public Administrations.
20
Project Management System
NIC
1.2 Project Description
The System to be developed will be reffered as Pproject Management System(PMS). The concept behind this project is to have a software which will provide the web application to keep a track of the paid projects so that it can be operate in the intranet of the NIC there is so many DDO‘S Across the India that is they can view from there location about the Status of the project that how much fund have allocated what is the amount which is spent and against what . The total flow of the money will be easily handled by the DDO‘S.
User Validation. Select The whole Entry for a Particular project at a time. Select The Entry for a Particular project year wise. Insert the New entries for Any project year wise. Update the Value in the Financial year by mean of Textbox. Delete the entries from the DataBase.
21
Project Management System
NIC
User can write their Queies .
User Validation: Will Validate the user that the user is authentic or not if a user is given the
correct user name and the password than only the user can enter to the and she/he can do the other this with the project . Select The whole entry for a particular project at a time: by mean of the user can see the full detail for a particular project in each in which the transaction made. Select The Entry for a Particular project year wise: by mean of the user can see and view the entries of the regarding in a given specific year . Insert the New entries for Any project year wise : The entries Can be made by the the DDO‘s for the with full details and that entries refelect into the database for the further use.
Update the Value in the Financial year by mean of Textbox:
In this the user can edit the
entries by the mean of text boxes a user can click on edit button the data in the DataGrid then in the specific row the textbox appears.After that a user can edit in the boxes and that data will be saved in the database for the further use.
22
Project Management System
NIC
Delete the entries from the DataBase. The user can delete the Selected row which she /he don’t want to be kept in the database.In the DataGrid button column these operation are performed. User can write their Queies : The user can pass their queries by mean of textboxes. And the result will be displayed in the datagrid.
1.3 System Requirements Hardware
Intel Pentium® Third processor or Higher Minimum 256 MB memory Recommended 512 MB Memory CD ROM Drive
Software
Microsoft Windows 2000® Server with Service Pack 3 or 4 (Server Side) Visual Studio .NET Version 1.1 or above MS SQL Server 2000
1.4 Tools & Technology Used
Technologies and tools are strongly related to the approach of software development. What the tools can or cannot do significantly impact what principles that can be used, as well as what objectives that can be fulfilled. While selection of a particular methodology may imply use of certain tools, the tools themselves often leave significant room for developers to choose how to use them. The selection has therefore been based mainly on the objectives of the project, while the methodologies were selected.
.NET Architecture
23
Project Management System
NIC
.NET security is not an island of technology, but a slice of a larger entity called the .NET Framework. Basic understanding of the .NET Framework is required before attempting .NET security programming. This chapter presents the basic concepts of the .NET Framework architecture and programming. This is an overview and is not intended to replace the independent study required for a mastery of this subject. Microsoft .NET is not just a different spin on the Win32 operating model. Furthermore, despite reports to the contrary, it is not Java in wolf‘s clothing. You will never understand or adequately explain .NET simply by comparing it to existing products. .NET is new. As such, .NET introduces a fresh operating modality and perspective on computing software and devices. Are there similarities to Java? Are there similarities to Win32? Yes, but there are many more differences. Successfully programming in .NET requires embracing this new technology as new and fully understanding the many things that make .NET unique. When object-oriented languages were introduced, developers faced a similar challenge and, unfortunately, mindset. Many programmers quickly learned the syntax and ported their C application to C++ or SmallTalk. However, without the requisite understanding of object-oriented programming, these new applications were procedural programs draped in the syntax of an object-oriented language. Some developers invested the time to learn object-oriented programming—not just the syntax, but the philosophy and intent. Their resulting applications were true object-oriented programs that provided all the benefits envisioned for the new programming modality. Similarly, understanding the philosophy and architecture of .NET is essential for creating applications that offer new solutions. Some industry analysts assert that Microsoft has gambled the company on .NET. I would not agree. .NET does represent a massive investment. However, Microsoft is a diversified and multibillion dollar company with many products and a sizable market share in many segments of the software industry. In addition, Microsoft is no longer simply a software company, having expanded into many markets outside their traditional stronghold. 24
Project Management System
NIC
But recognizing that Microsoft is not teetering on a precipice named .NET does not diminish the importance of .NET. .NET does represent a new philosophy in product development. From .NET will emerge an entirely new family of products that will drive Microsoft sales into the stratosphere over the next 5 to 10 years. If the .NET initiative fails, or more likely is adopted slowly, Microsoft will recover and continue, although maybe with a little less luster. Importantly, .NET allows Microsoft to escape the Windows conundrum. Although Windows
has been enormously successful, it is still a box. .NET helps Microsoft emerge from that box and develop applications for a universal audience. This new opportunity will fuel growth not just for Microsoft, but for software developers everywhere. I attended the formal launch of Microsoft .NET at the Professional Developers Conference in Orlando, Florida several years ago. William Gates III (aka Bill) was the keynote speaker. Part of his speech included an entertaining video. The video portrayed .NET as a new standard that will allow software to run anywhere, at anytime, on any platform, and on devices large and small.
Anywhere. This has reported many times, but it is worth repeating: ―Microsoft was late to realize the importance and then embrace the Internet.‖ Recently, Microsoft has been making up for that late start. .NET marks the next major step in that journey. The Internet is not an adjunct of .NET, but is interwoven seamlessly into the product. The Internet was planned, integrated, and implemented into .NET—including the embracing of open standards such as XML and HTTP. Essentially, any platform that offers a browser that understands XML or HTML is a potential .NET client. Anytime. The Internet is open 7 days per week and 24 hours per day. The 25
Project Management System
NIC
Internet never closes. Since .NET leverages the Internet, .NET applications such as a Web service are fully accessible at anytime. Any platform. .NET is a multilanguage and multiplatform operating environment. Compare this to Java, which is single-language and multiplatform. .NET offers C#, Visual Basic .NET, and many more .NET-compliant languages. Programming in .NET does not require learning an entirely new language. To program to the Java Virtual Machine (JVM) requires learning the Java language. For many, this is a substantial drawback. The common language runtime is the common runtime of all .NET languages. In addition, Microsoft publishes the Common Language Infrastructure (CLI) document, which is a set of guidelines for creating a .NET common language runtime for any platform, such as Linux. To view one such initiative, In the future, developers can create .NET applications in Windows and run them in Linux, Unix, Macintosh, or any platform that offers a common language runtime.
Devices large and small . NET marks Microsoft‘s first extensive support of
open standards, even if it is rather tepid. Microsoft adopts HTTP, SMTP, SOAP, XML, and many more standards. This means that any device that supports these standards can actively participate in a .NET conversation. This will liberate personal digital assistants (PDAs), hand-held, and embedded devices. These devices lack the girth to run powerful applications, such as full-blown Microsoft Office. Using open standards, these devices can tap the power of a back-end server and run virtually any program.
26
Project Management System
NIC
The embedded chip in your refrigerator could access Microsoft Word remotely, compose a grocery list, and print it to a networked printer. Refrigerators with word-processing capabilities—way cool!
.NET Is Web Enabled
Microsoft .NET is Web empowered. Developers can use ASP.NET, XML Web services, and ADO.NET to easily create feature-rich Web applications. This represents the front, middle, and bottom tier of an n-tiered enterprise application. Despite this, do not believe the rhetoric stating that Microsoft has abandoned client-side applications—some applications will never be well suited for server-side operations. Windows Forms, a new forms generation engine, and other additions in the .NET Framework make development of traditional Windows applications more intuitive, while adding additional features.
.NET Components
.NET introduces a new component model that is largely implicit. The messiness of COM (Component Object Model) is removed. In .NET, developers use standard language syntax to create, publish, and export components. There is nothing else to learn. .NET addresses many of the shortfalls of COM, including susceptibility to DLL Hell, language incompatibilities, reference counting, and more.
.
Coding COM at the API level is exacting. Interfaces such as IUnknown, IDispatch,
IConnectionPoint, and system functions such as CoGetClassObject and CoFreeUnusedLibraries represent a massive learning curve. MFC (Microsoft Foundation Classes), ATL (Active Template Library), and Visual Basic provided some relief, but offered different solutions for creating COM objects for different languages. How do you create a component in .NET? In the server application, you define
27
Project Management System
NIC
a public class, using the syntax of the preferred .NET language. In the client, you import a reference to the component application and then create an instance of the component class. That is it. You can then use the component. The arcane syntax of COM is gone. The developer controls the lifetime of a COM object. AddRef and Release live
in infamy. They are methods of the IUnknown interface and control the persistence of the COM object. If implemented incorrectly, a COM object could be released prematurely or, conversely, never be released and be the source of memory leaks. The .NET memory manager, appropriately named the Garbage Collector, is responsible for managing component lifetimes for the application— no more AddRef and Release. COM was largely a Windows standard, and building bridges to components in other platforms was difficult. COM was still a worthwhile endeavor and did indeed advance the concept of component development. However, now the torch has been handed to .NET. Using open standards, .NET components are potentially accessible to everyone at anytime. Component versioning was a considerable problem with COM and contributed to DLL Hell. Another contributor was COM‘s reliance on the Windows Registry. Let us assume that two versions of the same in-process server (COM DLL) are installed on the same computer, and the newer version is installed first. The older version will override the Registry settings of the newer component, and clients will be redirected to the incorrect version. Clients using newer services will immediately break. .NET does not rely on the Registry for component registration, which diminishes the possibility of DLL Hell. I have been teaching .NET to developers for some time and usually start class with a question for my students: Can someone describe the benefits of .NET 28
Project Management System
NIC
for end users? Students quickly mention the common language runtime, ASP.NET, XML integration, Garbage Collection, and so on. They are all great things, but they benefit programmers rather than end users. Why would clients give a whit about .NET? The benefit of .NET to users is the new generation of software that .NET introduces: software that runs anywhere, at anytime, on any platform, and from devices large and small.
.NET Framework Architecture
.NET is tiered, modular, and hierarchal. Each tier of the .NET Framework is a layer of abstraction. .NET languages are the top tier and the most abstracted level. The common language runtime is the bottom tier, the least abstracted,
29
Project Management System
NIC
and closest to the native environment. This is important since the common language runtime works closely with the operating environment to manage .NET applications. The .NET Framework is partitioned into modules, each with its own distinct responsibility. Finally, since higher tiers request services only from the lower tiers, .NET is hierarchal. The architectural layout of the .NET
.NET Framework architecture
The .NET Framework is a managed environment. The common language runtime monitors the execution of .NET applications and provides essential services. It manages memory, handles exceptions, ensures that applications are well-behaved, and much more. Language interoperability is one goal of .NET. .NET languages share a common runtime (the common language runtime, a common class library), the Framework Class Library (FCL), a common component model, and common
30
Project Management System
NIC
types. In .NET, the programming language is a lifestyle choice. Except for subtle differences, C#, VB.NET, or JScript.NET offer a similar experience. .NET abstracts lower-level services, while retaining most of their flexibility. This is important to C-based programmers, who shudder at the limitations presented in Visual Basic 6 and earlier. Let us examine each tier of the .NET Framework as it relates to a managed environment, language interoperability, and abstraction of lower-level services.
Common Abbreviated Names
There are a lot of new names in the .Net world. I'll introduce them now, both to help orient you before getting into the details, and so that I can make cross-references without having to add distracting definitions of each new term as it comes up.
The Common Language Runtime [CLR] is the managed code environment that everything else is built on. .Net is a garbage-collected environment but never interpreted - while .Net uses byte codes like Java, the Common Intermediate Language [CIL] code is always compiled, usually Just In Time [JIT] to be executed. (Yes, just like Java.) The Delphi compiler guys say that the jitter [the JIT compiler] compiles CIL about as fast as Delphi compiles Object Pascal, and that the object code that the jitter puts out is a lot like Delphi's object code. Only better, because the jitter can do function inlining. The Common Type System [CTS] provides basic value types, type composition, type safety, objects, interfaces, and delegates. (Delegates are a multi-cast version of Delphi's events.) The Common Language Specification [CLS] is the subset of the Common Type System that all first 31
Project Management System
NIC
class .Net languages need to share. Two .Net languages that have the same non-CLS type - like unsigned integers - can share values of that type, but there will be .Net languages which can't understand them. For example, Visual Basic doesn't have unsigned integers. The .Net framework classes are the new run-time library, an object-oriented API roughly the same size as the Delphi BPL's. The framework consists of thousands of CLS-compliant C# classes that do just about everything from GUI programming to file IO to web services.
Managed Languages and Common Language Specification
.NET supports managed and unmanaged programming languages. Applications created from managed languages, such as C# and VB.NET, execute under the management of a common runtime, called the common language runtime. There are several differences between a compiled managed application and an unmanaged program. ■■ Managed applications compile to Microsoft Intermediate Language (MSIL) and metadata. MSIL is a low-level language that all managed languages compile to instead of native binary. Using just-in-time compilation, at code execution, MSIL is converted into binary optimized both to the environment and the hardware. Since all managed languages ultimately become MSIL, there is a high degree of language interoperability in .NET. ■■ Metadata is data that describes data. In a managed application, also called an assembly, metadata formally defines the types employed by the program. ■■ Wave a fond goodbye to the Registry. Managed applications are sweeping away the Registry, Interface Definition Language (IDL) files, and type libraries with a single concept called metadata. Metadata and the related manifest describe the overall assembly and the specific types of an assembly.
32
Project Management System
NIC
Chapter ■■ Managed applications have limited exposure to the unmanaged environment. This might be frustrating to many programmers, particularly experienced C gurus. However, .NET has considerable flexibility. For those determined to use unmanaged code, there are interoperability services.
NOTE
In .NET, a managed application is called an assembly. An assembly adheres to the traditional Portable Executable (PE) format but contains additional headers and sections specific to .NET. MSIL and metadata are the most important new additions to the .NET PE. When the .NET Framework is installed, a new program loader recognizes and interprets the .NET PE format. In future Windows operating systems, the first being .NET Server, the .NET loader is automatically provided.
What is a managed language? If someone wants to create Forth.NET, are there established guidelines? Common Language Specification (CLS) is a set of specifications or guidelines defining a .NET language. Shared specifications promote language interoperability. For example, CLS defines the common types of managed languages, which is a subset of the Common Type System (CTS). This removes the issue of marshaling, a major impediment when working between two languages.
33
Project Management System
NIC
Common Type System
The Common Type System (CTS) is a catalog of .NET types—System.Int32, System.Decimal, System.Boolean, and so on. Developers are not required to use these types directly. These types are the underlying objects of the specific data types provided in each managed language. The following is the code for declaring an integer in C# and Visual Basic .NET. Either syntax maps to a System. Int32 object. // C# integer int nVar=0; ‗ VB.NET dim nVar as integer=0 Preferably, you should use the syntax of the language and not the underlying object type, leaving .NET the flexibility to select the most appropriate type and size for the operating environment. The common type system is a pyramid with System.Object at the apex. .NET types are separated into value and reference types. Value types, which are mainly primitive types, inherit from System.ValueType and then System.Object. Reference types—anything not a value type—are derived from System.Object, either directly or indirectly. Value types are short-term objects and are allocated on the stack. Reference types are essentially pointers and allocated on the managed heap. The lifetime of reference types is controlled by the Garbage Collector.
NOTE
There are many more differences between a value type and reference types, which is a subject beyond the context of this book. Value types can be converted to reference types, and vice versa, through processes called boxing and unboxing, respectively. Boxing is helpful when a developer needs to change the memory model of an object. The contributions of CTS extend well beyond the definitions of common data
34
Project Management System
NIC
types. CTS helps with type safeness, enhances language interoperability, aids in segregating application domains, and more. Type verification occurs during just-in-time compilation, ensures that MSIL safely accesses memory, and confirms that there is no attempt to access memory that is not formerly defined in metadata. If so, the code is treated as a rogue application. CTS provides a shared type substratum for .NET, enhancing language interoperability. Finally, .NET introduces lightweight processes called application domains. Application domains are processes within a process. Application domains are more scalable and less expensive then traditional Win32 processes. .NET must police application domains and guarantee that they are good neighbors. Code verification, type safeness, and CTS play a role in guaranteeing that application domains are safe.
.NET Framework Class Library
The .NET Framework Class Library (FCL) is a set of managed classes that provide access to system services. File input/output, sockets, database access, remoting, and XML are just some of the services available in the FCL. Importantly, all the .NET languages rely on the same managed classes for the same services. This is one of the reasons that, once you have learned any .NET language, you have learned 40 percent of every other managed language. The same classes, methods, parameters, and types are used for system services regardless of the language. This is one of the most important contributions of FCL. Both versions of the program are nearly identical. The primary difference is that C# uses semicolons at the end of statements, while VB.NET does not. The syntax and use of StreamReader, StreamWriter, and the Console class are identical: same methods, identical parameters, and consistent results. FCL includes some 600 managed classes. Aflat hierarchy consisting of hundreds of classes would be difficult to navigate. Microsoft partitioned the managed 35
Project Management System
NIC
classes of FCL into separate namespaces based on functionality. For example, classes pertaining to local input/output can be found in the namespace System. IO. To further refine the hierarchy, FCL namespaces are often nested; the .NET tiers of namespaces are delimited with dots. System.Runtime.InteropServices, System.Security.Permissions, and System.Windows.Forms are examples of nested namespaces. The root namespace is System, which provides classes for console input/output, management of application domains, delegates, garbage collection, and more. Prefixing calls with the namespace can get quite cumbersome. You can avoid needless typing with the using statement, and the namespace is implicit. If two namespaces contain identically named classes, an ambiguity may arise from the using statement. Workarounds for class name ambiguity are provided by defining unique names with the using directive It is hard to avoid the FCL and write a meaningful .NET application. Developers should fight the tendency or inclination to jump to unmanaged code for services provided in .NET. It may appear simpler because you have used that unmanaged API a hundred times. However, your program then becomes less portable, and security issues may arise later. When in Rome, do as the Romans do. When in .NET, use managed code.
36
Project Management System
NIC
ASP.NET
ASP.NET is used to create dynamic Web applications and is the successor to ASP. While IIS 5 and 6 support side-by-side execution of ASP and ASP.NET, ASP.NET is not merely an upgrade of ASP, as evidenced by the lack of upward compatibility. The view state, configuration files, validation controls, and a total reconstruction of the ASP architecture is the short list of numerous changes. The theme of these changes is scalability, extensibility, and improving the programmer experience. Microsoft emphasizes scalability in ASP.NET. Free threads boost responsiveness and prevent internal bottlenecks. ASP.NET uses ADO.NET, server-side controls, and other techniques to promote a highly distributed and scalable model. Also, ASP.NET hosts Web applications in application domains within the worker process (aspnet_wp.exe) to heighten performance and lower overhead. Finally, ASP.NET uses compiled pages instead of interpreted pages to improve performance. Speaking of scripting languages, many developers did not learn ASP because of the necessity of learning yet another language. In addition, some C-based programmers have an aversion to scripting languages on principle, such as VBScript. ASP.NET is coded in the managed language of choice: C#, VB.NET, SmallTalk .NET, or whatever. The complication of learning a new language solely for Web development has been removed. There is an additional, probably unintentional, but positive side effect. Converting a client-side application written in a managed language to a Web-based program is considerably easier since the language now remains the same. This removes the final excuse for not moving all your applications to the Web. 37
Project Management System
NIC
NET Architecture
ASP.NET and replaces Visual Interdev. Web Forms closely resembles Windows Forms or the Visual Basic 6 forms engine, one more consideration that helps developers move between client and Web programming. A variety of serverand client-side controls are supported. Web Forms controls are server-side controls and typically more complex than HTML controls. The calendar control typifies a Web Form control that maps to multiple tags. HTML controls by default are client-side controls and map to a single tag. Web controls are instances of managed classes that write HTML tags. Developers create custom controls by having them inherit from the Control class and coding the Control. Render method to output desired tags. Developers can view and edit the generated HTML by switching to the HTML pane, shown in Figure 1.3. Actually, developers can opt out of the Web forms and build controls directly into the HTML pane or even Notepad.
XML Web Services
Web services are the basis of the programmable Web and distributed applications that transcend hardware and operating environments. Web services are not unique to Microsoft. Microsoft, IBM, Sun, and other vendors are promoting Web services as integral components of their recent initiatives. Web services promote remote function calls over the Internet. The promotion and hype surrounding Web services has been deafening. .NET Architec
A Web service exposes functionality to the entire world—any device at any time. Not coincidentally, this is the very definition of .NET and explains the importance of a Web server to .NET. Anyone with Web-enabled software, such as a browser, that understands HTML and HTTP can access a Web service. Any device, large or small, that is Web enabled can access a Web service. This revolutionizes embedded devices, bringing an array of services to these devices
38
Project Management System
NIC
that were not previously practical. The Internet never closes, which means that Web services are available 24/7. The explosion of computers and PDAs that are continuously wired to the Internet creates a burgeoning audience for Web services. XMLWeb services are part of ASP.NET and leverage open standards, such as HTTP and XML, to publish public functions to the Internet. In addition, creating Web services in .NET is remarkably easy. Web pages publish presentation data with limited functionality over the Internet. Open standards, namely HTML and HTTP, are the backbone of Web pages and deliver them to almost anyone with a browser. Web services expose functionality over the Internet using open standards—the combination of HTTP, XML, SOAP, and the Web Service Description Language (WSDL), which are the underpinning of this exciting technology. SOAP is the preferred protocol for XMLWeb services. Visual Studio .NET removes the challenge of creating a Web service. Developers can create Web services with limited or no knowledge of SOAP, XML, or WSDL. The first step is to create an ASP.NET Web service project. The new project is a starter kit for a Web service application. AWeb service class, sample Web method, web.config file, global.asx file, and the remaining plumbing of a Web service are provided. See Figure 1.4. The developer is left with only one task—writing the functions to be exposed as Web methods. Consuming a Web service is equally easy. Start by creating a proxy from the WSDL of the Web service. Create the proxy in Visual Studio .NET by adding a Web reference or externally using the WSDL.exe tool. After creating the proxy, compile it into the Web service client or into a separate assembly, and then bind it to the client. In the client code, create an instance of the proxy and call the Web service methods as local functions. The proxy connects to the Web service, uses SOAP to invoke a remote method, and then return any values. The parameters, return value, and other Web service data are transported in XML envelopes.
39
Project Management System
NIC
Windows Forms and Console Applications
Windows Forms is the form generator for client-side applications and is similar to the forms engine of Visual Basic 6. Visual Basic programmers using VB.NET will be familiar with the look and feel of Windows Forms, but this similarity is largely cosmetic and there are substantial differences in the implementation. Windows Forms is new to Visual C++ programmers, who previously had to code every aspect of a program‘s graphical user interface. This excludes the dialog editor of Visual C++, which is a limited forms engine. Microsoft Foundation Classes removed some of the drudgery, but it was far from a visual tool. C-based developers can now focus more on the application and less on the mechanics of creating edit boxes, coding buttons, managing a status bar, and attaching a menu to a window. Windows Forms is primarily a code generator, generating managed classes for forms, buttons, text boxes, menus, and other graphical user interface elements.
NOTE
C++ developers do not have access to Windows Forms as a forms generator. They are restricted to coding the graphical user interface from managed classes found in 40
Project Management System
NIC
the Windows.Forms namespace. There is no visual assistance. C-based programmers must use C# for full access to Windows Forms visual tools. Console applications have been available to C-based, but not to Visual Basic, programmers. In .NET, console applications are available to all managed languages. Console applications are useful for logging, instrumentation, and other text-based activities.
ADO.NET
ADO.NET is an exceptional and a worthy successor to ADO. ADO.NET accentuates disconnected data manipulation, is highly scalable, integrates open standards, and is perfected for Web application development. ADO.NET offers managed providers for Microsoft SQL and OLE DB databases and is a set of managed classes in the System.Data namespace. The System.Data.SqlClient namespace contains classes related to Microsoft SQL, while System.Data.OleDb encompasses classes pertaining to OLE DB providers. The differences between ADO.NET and ADO are significant. In ADO, everything revolves around record sets. ADO.NET does not support record sets, which underscores that there are fundamental differences between ADO.NET and ADO. ADO.NET is an entirely different model. Record sets, client-side cursors, and server-side cursors are not supported in ADO.NET. Instead, these constructs are replaced by data readers on the server side and data sets for client-side disconnected management of data. Data readers are server side, and support read-only and forward-only access of the database. Data sets are client side, bidirectional, and modifiable. ADO.NET is more scalable then its predecessor and embraces the disconnected model. Data sets are more flexible then records sets, supporting the client-side transfer of multiple tables and relations. The ability to transfer multiple tables of a database as a unit was not easily supported in ADO. With more 41
Project Management System
NIC
relevant data on the client side, the application can remain disconnected longer, which improves scalability and enhances customer satisfaction. XML is ubiquitous in the .NET Framework—no more so than in ADO.NET, where you bump into XML everywhere. Data sets particularly rely heavily on XML as the standard for transmitting data from the server to the client. In data sets, building relations between tables from different databases is trivial, since regardless of the origin, everything is ultimately XML. There is no concept of
Chapter
an SQL or OleDb dataset. When the data reaches the data set, it is fully homogenized. This provides ADO.NET with unprecedented flexibility. Data sets are initialized using data adapters. Data adapters play a critical role in ADO.NET and are the bridge between the data source and the client-side data set. The data adapter is the connection between the data source and the disconnected database. First, a data adapter fills the data set with content from the data source. Second, using command builder objects, data adapters update the data source with changes incurred in the data set. Data adapters are the glue that makes the disconnected model work. An ADO.NET data set is an ensemble of collections, beginning with the tables collection. Iterate the tables collection to find the individual tables stored in the data set. Each table has a rows collection and a data column collection. The rows collection contains the records of the table, while the data column collection is the schema of the table. Each row has a collection of values, normally called fields. Iterate the fields to extract the individual values of each record.
.NET Architecture
The Data toolbar of Visual Studio .NET shown in Figure 1.5 provides a full complement of controls for rapid application development using ADO.NET. ADO.NET code can be complicated and long. The data tools generate the code for you and can be a welcome time saver.
42
Project Management System
NIC
.NET Remoting
.NET Remoting is a second option for remoting objects in the .NET Framework. The first mentioned was XMLWeb services. .NET Remoting is similar to Web services conceptually. However, with .NET Remoting the developer chooses the transmission protocol, data protocol, data port, and other aspects of the remoting architecture necessary to open a channel for client-server communication. In essence, a developer is setting the specifications of the remoting infrastructure. In this way, .NET Remoting offers unlimited possibilities. Like Web services, .NET Remoting can leverage open standards, such as XML, HTTP, and SMTP. .NET Remoting is fully extensible. Custom or and proprietary standards can also be plugged in. The namespace for .NET Remoting is System.Runtime.Remoting. Remoted objects can be copied or used as a reference (marshal-by-reference). If copied, the object is duplicated in the address area of the client and is then accessible as a local object. Alternately, remoted objects can be accessed by reference via a proxy that connects to the object on the server machine. The indirection of a proxy affects performance. However, not all remoted objects are good candidates for copying. Some are either too large, have software dependencies on the server side, or require the server machine.
43
Project Management System
NIC
For server-side or referenced objects, .NET controls the activation of remoted objects as either Singleton or SingleCall objects. Singleton objects are created once, then shared among multiple clients.
System Analysis
2.1 Information Gathering
Information about the Firm: National Informatics Centre (NIC) is a premiere organization of the Government of India in the field of Informatics Services and Information Technology (IT) applications, and has been instrumental in steering Information and Communication Technology (ICT) applications in Government Departments at Central, State and Districts in government services, wider transparency in government functions, and improvement in decentralized planning and management. Information about Project: During the analysis, we collected whole information from ―Mrs. Rachna Srivastava‖ who is working as Technical Director and Mrs. Vinita Grewal, Senior Systems Analyst and other the staff members in the training division at National Informatics Center, New Delhi. Information Gathering Tools: We have collected the information about the current system from: Reports Personnel Staff System Documentation & Manuals Trainees 13
2.2 Existing System
Existing Manual System
44
Project Management System
NIC
The employment exchanges provide facilities for registration, vacancy, submission, meeting queries etc. The State Directorates for all the exchanges in the State keep the database of job seekers, vacancies notified by Government/Private sector employers and vocational guidance information. They are responsible for the implementation of the Employment Exchange procedures and other employment generation schemes. The consolidated reports are maintained at DGET Headquarters. The manual system comprises of manual procedures in most of the employment exchanges. In the manual system, the main problems faced are time lag & accuracy, maintenance of records, and deviations from uniform procedures. Existing Computerised System The computerised systems comprises of partially computerised and partially manual procedures implemented by some of the employment exchanges in several states. In computerised system, all the activities are not addressed; MIS and returns compilation is up to some extent; multiple platforms are used; technological advancement needs has resulted in duplication of efforts and maintenance problems in many States with partial networking. There is no uniformity of platforms for development and deployment, since they are developed by various agencies either from the state or NIC centres; they have used multiple platforms for development and deployment. Currently, in different states/UTs, five different platforms are being used for running computerized exchanges viz. UNIX / Oracle, UNIX / COBOL, UNIX / Foxplus, Windows / SQL Server, Windows / MS Access with PCs / Terminals. The application software has also been developed using different development tools namely Oracle, SQL Server, Active Server Pages, Visual Basic, Power Builder, MS Access, Foxplus, and COBOL.
CIL
All .Net languages compile to CIL. (CIL was once known as Microsoft Intermediate Language, or MSIL.) .Net programs compile to something called an assembly, which is a standard PE [Portable Executable] exe or dll that contains a special header that says that the PE file contains CIL and .Net metadata instead of normal object code. Every entry point in the PE file is
45
Project Management System
NIC
populated with stub code that causes the CIL to be compiled to actual object code on an asneeded basis. Metadata is a lot like Delphi's RTTI, but even more extensive. Before JIT Each method is populated with stub code that compiles the CIL before running it. After JIT Each method is populated with actual object code.
Obviously, as-needed compilation does mean that the first call to a routine costs more than subsequent calls, but it's not a huge overhead both because CIL is so low-level and because the jitter doesn't have to handle parsing, linking, or macro expansion. Jitting also produces a couple of benefits. First, since the jitter only has to produce object code for a single machine, it can generate object code optimized for the machine it's running on. Second, there is a sense in which the jitter is a smart linker - code that is not used is not jitted and doesn't consume memory. .Net applications can use the "reflection" API to emit CIL at runtime. This generated code will be jitted when called, just like any other CIL code. This lets spreadsheets and script languages compile expressions to CIL, which is in turn compiled on down to object code.
Common Language Runtime
The common language runtime is the engine of .NET and the common runtime of all managed languages. In addition, as the final layer resting atop of the operating environment, the CLR provides the first level of abstraction. Since assemblies run within the context of the common language runtime, they are independent of the underlying operating environment and hardware. Assemblies or managed code are portable to any environment offering a .NETcompliant
46
Project Management System
NIC
common language runtime, as defined by the Common Language Infrastructure (CLI). Managed code is managed by the common language runtime. common language runtime manages security, code verification, type verification, exception handling, garbage collection, a common runtime, and other important elements of program execution. When an assembly is executed, mscoree.dll is loaded into the memory of the running process, and the imported entry point _CorExeMain is called. Mscoree contains the common language runtime, which then manages the executing application. Of the many services offered by the common language runtime, we will focus on the two most important: code execution and memory management.
Just-in-Time Compilation
Assemblies contain MSIL, which is converted into native binary and executed at runtime, using a process aptly named Just-in-Time compilation, or jitting. An assembly is subjected to two compilations. First, managed code is compiled to create the actual assembly. Managed compilers, such as csc and vbc, .NET compile C# and VB.NET source code into an assembly that contains MSIL and metadata. Second, the assembly is compiled at load time, converting the MSIL into native binary that is optimized for the current platform and hardware. When an assembly is jitted, an in-memory cache of the binary is created and executed. Just-in-Time compilers are called Jitters. There is a Jitter for each supported hardware architecture. Converting an entire program to native binary may be inefficient and compromise
47
Project Management System
NIC
the performance of the application. The Jitter converts to binary only methods that are called; there‘s no need to convert methods that are never used to native code. Only the parts of the program used during the current execution are loaded into memory, which conserves resources. When the assembly is loaded, the class loader stubs the methods of each class. At this time, the stubs point to a Jitter routine that converts MSIL to native binary. Upon invocation of a stubbed method, the conversion routine is called that compiles MSIL into native binary, which is then cached in memory. The stub is then updated to point to the in-memory location of the native binary and the code is executed. Future calls to the same function skip the conversion routine and execute the native binary directly. If you chart the runtime performance of a jitted assembly, you will see a series of small peaks and valleys. Based on usage patterns, the type of application, and the size of the application, this may not be the most efficient model for executing the assembly. Consider a large application in which the user touches 80 percent of the functionality and where performance is a concern. A few peaks and valleys may not be noticeable, but a few hundred might be problematic. In this scenario, a different model will work better. In the alternate model, you compile and cache the native binary of the entire assembly. Running the assembly from the cache should improve performance. Instead of a blizzard of peaks and valleys, the new chart would show an acute spike at the beginning and then flat line for the remainder of the program. To adopt the later model, use the Ngen tool to generate the cached native image of the .NET assembly.
Garbage Collector
In .NET, the Garbage Collector manages the memory associated with new objects. Ceding memory management to the runtime is not a radical concept 48
Project Management System
NIC
for Visual Basic programmers. However, this is indeed a radical concept for Cbased programmers accustomed to managing their own memory. Despite the messiness, C-based programmers relish pointers. This approach will also be foreign to low-level COM programmers, who are accustomed to the IUnknown interface and to calling the AddRef and Release methods to manage the lifetime of components. However, I believe there will be few COM programmers marching to protest the lost of AddRef and Release—these methods have never been a developer favorite. The Garbage Collector will hopefully eviscerate inadvertent memory leaks or problems caused by prematurely releasing an object. Memory management, regardless of the application, typical follows known patterns. There is absolutely no reason for every developer to implement a private memory management model. The Garbage Collector implements a common memory model that is applied to all managed code. The public interface of the Garbage Collector is the System.GC managed class. Garbage collection manages the heap using a concept called generations, which is based on certain tenets: ■■ Small objects are generally short lived and frequently accessed. ■■ Larger objects are longer lived. ■■ Grouping like-sized objects together decreases heap fragmentation. ■■ Segmenting the heap offers efficiencies, such as defragmenting only a portion of the heap. The managed heap is divided into generations. As new objects are created, they are placed in Generation 0. Eventually, memory reserved for Generation 0 will be exhausted. The generation is then compacted. If these steps do not free enough memory to satisfy the pending allocation request, the current generation is aged to Generation 1 and a new Generation 0 is started. Existing objects are now in Generation 1, and the pending object is allocated in the new Generation 0. The next time memory is depleted, these steps are repeated, now for Generation 0 and 1. If insufficient memory is recovered, the existing generations
are aged and Generation 0 is reinitialized. 49
Project Management System
NIC
There are a maximum of three generations: Generation 0, 1, and 2. Sufficiently, large objects (larger than 20,000 bytes) are automatically copied to the large object heap, which is Generation 2. This model keeps short-lived objects group together in younger generations. Large objects are group in older generations. In addition, the smaller objects, which require more frequent aligning, can be compacted without having to recompact the entire heap. In C#, a developer allocates memory for an object with the new statement. The Garbage Collector creates the object on the managed heap. However, there is no free or delete command to deterministically remove the object from memory. Cleanup of .NET objects is nondeterministic. When there are no outstanding references to the object, the Garbage Collector eventually removes the object from the managed heap. At that time, if the object has a destructor, the destructor is called and the object is afforded the opportunity to release unmanaged resources. This includes closing files, releasing tokens, and deconstructing socket connections. .NET Starting at the initialization, objects with destructors are weighted with nontrivial additional overhead. The management of objects with destructors at times seems counterintuitive and destined to draw the wrath of many developers. This is a perfect example of what happens when a good idea goes afoul. When an object with a destructor is instantiated, not only is the object allocated on the managed heap, but also a reference to the object is placed in the finalization queue. When there are no outstanding references to the object, the Garbage Collector does not immediately remove the object, as it would an object without a destructor. It spends the garbage collection cycle moving the object from the finalization queue to the freachable queue. The freachable queue contains references to objects pending finalization. There is a dedicated thread that services the freachable queue. This thread eventually wakes up and calls the destructors of objects found in the freachable queue. On the next cycle of garbage collection, these objects are finally deleted. Destructors should be omitted from all .NET objects unless required. Alternately, consider 50
Project Management System
NIC
using an IDisposable.Dispose method, which can be called deterministically, without the overhead of a destructor.
Language features
C# is, in some senses, the programming language which most directly reflects the underlying Common Language Runtime (CLR) on which all .NET programs run, and it depends strongly on this framework because it was designed specifically to take advantage of the features that the CLR provides. Most of C#'s intrinsic types all correspond to value-types implemented by the .NET Framework. A common misbelief is that they are garbage-collected, though they are not; they are true value-types and are stack allocated (with an exception for System.Object, and due to interning, System.String). Applications written in C# require an implementation of the CLR to execute, in the same way that VB6 requires a runtime to execute (this is often confused with the JRE, which provides a byte-code interpreter, unlike Java classes .NET programs are 2-pass compiled, stored as first-pass binary code and second-pass compiled at the client workstation. Java programs require a Java Virtual Machine. VB6 Programs require a support library, likewise, .NET programs require a set of support libraries and a core execution environment (which handles the initialization and initial JIT process.) Compared to C and C++, the language is restricted or enhanced in a number of ways, including but not limited to the following: Pointers can only be within an unsafe scope, and only programs with appropriate permissions can execute code marked as unsafe. Most object access is done through safe references, which cannot be made invalid, and most arithmetic is checked for overflow. Pointers can only be made to so-called value types; objects managed by the garbage collector can only be referred to. An unsafe pointer can be made to not only value-types, but to subclasses of System.Object as well. Also safe code can be written that uses a pointer (System.IntPtr) however no direct manipulation of the memory at the stored address can be performed from C# without the unsafe and fixed keywords, unless calls to Win32 API functions such as rtlMoveMemory are made.
51
Project Management System
NIC
Managed memory cannot be explicitly freed, but instead is garbage collected when no more references to the memory exists. (Objects that reference unmanaged resources, such as an HBRUSH, can be instructed to release those resources through the standard IDisposable interface, which provides a pattern for deterministic deallocation of resources.) Only single inheritance is available, but a class can implement any number of interfaces. This was a design decision by the languages lead architect (Anders Hejlsberg) to avoid complication, avoid 'dependancy hell' and simplify architectural requirements throughout the CLR. C# is more typesafe than C++. The only implicit conversions by default are safe conversions, such as widening of integers and conversion from a derived type to a base type (and this is enforced at compile and, indirectly, during JIT). There are no implicit conversions between booleans and integers, between enumeration members and integers, no void pointers (although references to an Object are similar), and any user-defined implicit conversion must be explicitly marked as such, unlike C++'s copy constructors. Syntax for array declaration is different ("int[] a = new int[5];" instead of "int a[5];"). Enumeration members are placed in their own namespace. C# V1 lacks templates, however, C# V2 provides generics. Properties are available which results in syntax that resembles C++ member field access, similar to VB. Full type reflection and discovery is available.
System Analysis
2.1 Information Gathering
Information about the Firm:
52
Project Management System
NIC
National Informatics Centre (NIC) is a premiere organization of the Government of India in the field of Informatics Services and Information Technology (IT) applications, and has been instrumental in steering Information and Communication Technology (ICT) applications in Government Departments at Central, State and Districts in government services, wider transparency in government functions, and improvement in decentralized planning and management. Information about Project: The information about the project is provided by our project guides, each and every detail is provided by Mr Pradeep Singh . Information Gathering Tools: We have collected the information about the current system from: Reports Personnel Staff System Documentation & Manuals 13
2.2 Existing System
Existing System The existing system is the Visual Basic the system is running in a well and effective manner .
2.3 Proposed System
The proposed system will going to be a web application so that it can be available on the intranet
53
Project Management System
NIC
2.4 Feasibility Study
System feasibility explains the likelihood that the system will be beneficial to the organization. We did following feasibility test: Technical feasibility Operational feasibility Economical feasibility Technical Feasibility It involves determining whether or not a system can actually be constructed to solve the problem at hand. The technical issues raised during the feasibility stage of the investigation were: N.I.C. has well equipped Labs 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. The proposed application will provide all the necessary information to all the users on web. 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 Operational Feasibility Proposed projects are of course beneficial only if can be turned into information systems that will meet the organization‘s operating requirements. Following questions helped us to test the operational feasibility of system: Is there sufficient support for the project from management? Yes, there is full support from management for the project.
54
Project Management System
NIC
Are current business methods acceptable to the users? No, the users are not satisfied with the current system. They welcome a change that will bring about a more operational and useful system. Presently they have to devote large amount of time in handling employment request manually, more paper work is included which will now avoided using this automated project. Economical Feasibility It involves estimating the benefits and costs. These benefits and costs may be tangible or intangible.
Software Requirement Specifications
4.2 Database Design
55
Project Management System
NIC
Field Name Budget head Major_head Desc_no Sub_head Head_code Desc Desc_short Fin_year Print_code Allocation Code Regis_Prin Exp_inclu Exp_9293 Exp_9394 Exp_9495 Exp_9596 Exp_9697 Exp_9798 Exp_9899 Exp_9900 Exp_0001 Exp_0102 Exp_0203 Exp_0304 Exp_0405 Exp_0506 Nic_others
Data Type nvarchar nvarchar nvarchar nvarchar nvarchar nvarchar nvarchar nvarchar nvarchar float float float float float float float float float float float float float float float float float float float
Size 1 10 8 25 20 60 15 9 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
Bu d0 506
Ue sr
Field_Name
Data_Type
Size
Null 56
Project Management System
NIC
Userid userpwd nvarchar nvarchar 30 30 NOT NOT
Proj_exp
Field_Name Desc_no Ddo_code Exp_date Exp_amt Data_Type numeric numeric nvarchar numeric Size 9(18,2) 9(18,2) 50 9(18,2) Null NOT NOT NOT NOT
Proj_lc
Field_Name Desc_no Ddo_code Lc_amount Lc_Date Lc__Sancno Data_Type numeric numeric numeric nvarchar nvarchar Size 9(18,2) 9(18,2) 9(18,2) 50 50 Null NOT NOT NOT NOT NOT
Fvcb9293
Field_Name Data_Type Size Null 57
Project Management System
NIC
Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Amount Sancno Sancdt Sancamt Billtype Appropriat Exp_incl Balance Remarks Cheque1 Cheq_paid Revenue Dvno Adj_bno Adj_amt Net_amt Grant_code int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar float nvarchar smalldatetime float nvarchar float float float nvarchar nvarchar nvarchar nvarchar float nvarchar float float float 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 8 22 4 8 1 8 8 8 60 90 1 1 8 25 8 8 8 NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
Fvcb9394
58
Project Management System
NIC
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Amount Sancno Sancdt Sancamt Billtype Appropriat Exp_incl Balance Remarks Cheque1 Cheq_paid Revenue Dvno Adj_bno Adj_amt Net_amt Grant_code Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar float nvarchar smalldatetime float nvarchar float float float nvarchar nvarchar nvarchar nvarchar float nvarchar float float float Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 8 22 4 8 1 8 8 8 60 90 1 1 8 25 8 8 8 Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
59
Project Management System
NIC
Fvcb9495
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Amount Sancno Sancdt Sancamt Billtype Appropriat Exp_incl Balance Remarks Cheque1 Cheq_paid Revenue Dvno Adj_bno Adj_amt Net_amt Grant_code Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar float nvarchar smalldatetime float nvarchar float float float nvarchar nvarchar nvarchar nvarchar float nvarchar float float float Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 8 22 4 8 1 8 8 8 60 90 1 1 8 25 8 8 8 Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
60
Project Management System
NIC
Fvcb9596
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Amount Sancno Sancdt Sancamt Billtype Appropriat Exp_incl Balance Remarks Cheque1 Cheq_paid Revenue Dvno Adj_bno Adj_amt Net_amt Grant_code Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar float nvarchar smalldatetime float nvarchar float float float nvarchar nvarchar nvarchar nvarchar float nvarchar float float float Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 8 22 4 8 1 8 8 8 60 90 1 1 8 25 8 8 8 Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
61
Project Management System
NIC
Fvcb9697
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Amount Sancno Sancdt Sancamt Billtype Appropriat Exp_incl Balance Remarks Cheque1 Cheq_paid Revenue Dvno Adj_bno Adj_amt Net_amt Grant_code Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar float nvarchar smalldatetime float nvarchar float float float nvarchar nvarchar nvarchar nvarchar float nvarchar float float float Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 8 22 4 8 1 8 8 8 60 90 1 1 8 25 8 8 8 Null Indentity NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
62
Project Management System
NIC
Fvcb9798
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Amount Sancno Sancdt Sancamt Billtype Appropriat Exp_incl Balance Remarks Cheque1 Cheq_paid Revenue Dvno Adj_bno Adj_amt Net_amt Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar float nvarchar smalldatetime float nvarchar float float float nvarchar nvarchar nvarchar nvarchar float nvarchar float float Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 8 22 4 8 1 8 8 8 60 90 1 1 8 25 8 8 Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT 63
Project Management System
NIC
Grant_code float 8 NOT
Fvcb9899
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Amount Sancno Sancdt Sancamt Billtype Appropriat Exp_incl Balance Remarks Cheque1 Cheq_paid Revenue Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar float nvarchar smalldatetime float nvarchar float float float nvarchar nvarchar nvarchar nvarchar Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 8 22 4 8 1 8 8 8 60 90 1 1 Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT 64
Project Management System
NIC
Dvno Adj_bno Adj_amt Net_amt Grant_code float nvarchar float float float 8 25 8 8 8 NOT NOT NOT NOT NOT
Fvcb9900
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Amount Sancno Sancdt Sancamt Billtype Appropriat Exp_incl Balance Remarks Cheque1 Cheq_paid Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar float nvarchar smalldatetime float nvarchar float float float nvarchar nvarchar nvarchar Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 8 22 4 8 1 8 8 8 60 90 1 Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
65
Project Management System
NIC
Revenue Dvno Adj_bno Adj_amt Net_amt Grant_code nvarchar float nvarchar float float float 1 8 25 8 8 8 NOT NOT NOT NOT NOT NOT
Fvcb0001
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Amount Sancno Sancdt Sancamt Billtype Appropriat Exp_incl Balance Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar float nvarchar smalldatetime float nvarchar float float float Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 8 22 4 8 1 8 8 8 Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT 66
Project Management System
NIC
Remarks Cheque1 Cheq_paid Revenue Dvno Adj_bno Adj_amt Net_amt Grant_code nvarchar nvarchar nvarchar nvarchar float nvarchar float float float 60 90 1 1 8 25 8 8 8 NOT NOT NOT NOT NOT NOT NOT NOT NOT
Fvcb0102
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Amount Sancno Sancdt Sancamt Billtype Appropriat Exp_incl Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar float nvarchar smalldatetime float nvarchar float float Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 8 22 4 8 1 8 8 Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT 67
Project Management System
NIC
Balance Remarks Cheque1 Cheq_paid Revenue Dvno Adj_bno Adj_amt Net_amt Grant_code float nvarchar nvarchar nvarchar nvarchar float nvarchar float float float 8 60 90 1 1 8 25 8 8 8 NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
Fvcb0203
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Amount Sancno Sancdt Sancamt Billtype Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar float nvarchar smalldatetime float nvarchar Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 8 22 4 8 1 Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT 68
Project Management System
NIC
Appropriat Exp_incl Balance Remarks Cheque1 Cheq_paid Revenue Dvno Adj_bno Adj_amt Net_amt Grant_code float float float nvarchar nvarchar nvarchar nvarchar float nvarchar float float float 8 8 8 60 90 1 1 8 25 8 8 8 NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
Fvcb0304
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Amount Sancno Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar float nvarchar Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 8 22 Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT 69
Project Management System
NIC
Sancdt Sancamt Billtype Appropriat Exp_incl Balance Remarks Cheque1 Cheq_paid Revenue Dvno Adj_bno Adj_amt Net_amt Grant_code smalldatetime float nvarchar float float float nvarchar nvarchar nvarchar nvarchar float nvarchar float float float 4 8 1 8 8 8 60 90 1 1 8 25 8 8 8 NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
Fvcb0405
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Purpose S_no Bill_no_co Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar nvarchar float nvarchar Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 50 8 25 Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
70
Project Management System
NIC
Amount Sancno Sancdt Sancamt Billtype Appropriat Exp_incl Balance Remarks Cheque1 Cheq_paid Revenue Dvno Adj_bno Adj_amt Net_amt Grant_code float nvarchar smalldatetime float nvarchar float float float nvarchar nvarchar nvarchar nvarchar float nvarchar float float float 8 22 4 8 1 8 8 8 60 90 1 1 8 25 8 8 8 NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
Fvcb0506
Field_Name Serial_no Code Dairy_no Emp_code Bill_no Bill_date Det_head Head Sub_head Minor_head Exp_code Month No_sub_vo Party_part Data_Type int nvarchar float float nvarchar smalldatetime float nvarchar nvarchar float float nvarchar float nvarchar Size 4 1 8 8 25 4 8 4 13 8 8 10 8 40 Null NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT 71
Project Management System
NIC
Purpose S_no Bill_no_co Amount Sancno Sancdt Sancamt Billtype Appropriat Exp_incl Balance Remarks Cheque1 Cheq_paid Revenue Dvno Adj_bno Adj_amt Net_amt Grant_code nvarchar float nvarchar float nvarchar smalldatetime float nvarchar float float float nvarchar nvarchar nvarchar nvarchar float nvarchar float float float 50 8 25 8 22 4 8 1 8 8 8 60 90 1 1 8 25 8 8 8 NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT NOT
4.4 Screen Shots
72
Project Management System
NIC
73
Project Management System
NIC
74
Project Management System
NIC Chapter
5
75
Project Management System
NIC
76
Project Management System
NIC
77
Project Management System
NIC
78
Project Management System
NIC
79
Project Management System
NIC
80
Project Management System
NIC
81
Project Management System
NIC
Conclusion
By designing the ―Project Management System‖ through the .NET Technology, upto some extend I able to solve the task that they personnel wants. According to my point of view I tried my label best as a trainee.As no body can say that this is the best because solution can be made more better . The Project Management System) is still taking shape, there are many more modules and functionalities left on this project as described in this text also.
Chapter
6
82
Project Management System
NIC
Bibliography
References:Quick Tutorial on Asp.Net: http://www.docs.aspng.com/quickstart/aspplus/ Coding support on Visual C#. NET: http://www.codeguru.com/Csharp/ http://msdn.microsoft.com/howto/webdev.asp/ http://www.yoda.arachsys.com/csharp/faq/ Book:Microsoft Visual C#. NET 2003 by Steven Holzner Publication by Pearson Education (Singapore) Detail log on to www.pearsoned.co.in 2. Beginning Visual C# by karli Watson, David Espinosa, zach Greenvoss, Christian Nagel, Eric White Publication Wrox Press Ltd. Detail log on to www.beginningdotnet.com 3. Microsoft SQL Server by Ron Soukup & Kalen Delaney Publication by WP Publisher & Distributors (p) Ltd. Microsoft Press log on www.microsoft.com
83
Project Management System
NIC For addition of CSS on web Page: http://support.microsoft.com/default.aspx/ For Web Designing Tool Kit 3rd Collection v1.1: http://www.usingit.com/order/index.html/
84