0 оценок0% нашли этот документ полезным (0 голосов)
13 просмотров45 страниц
TARINDER SINGH VINESH PAL 1arlnder Slngh Anu vlnesh Thal!REFACE this project report documents the EM!LOYEE MANAGEMENT SYSTEM. This is comprehensive application soItware that can maintain and handles all details oI the employee system used in any Iirm.
TARINDER SINGH VINESH PAL 1arlnder Slngh Anu vlnesh Thal!REFACE this project report documents the EM!LOYEE MANAGEMENT SYSTEM. This is comprehensive application soItware that can maintain and handles all details oI the employee system used in any Iirm.
Авторское право:
Attribution Non-Commercial (BY-NC)
Доступные форматы
Скачайте в формате DOCX, PDF, TXT или читайте онлайн в Scribd
TARINDER SINGH VINESH PAL 1arlnder Slngh Anu vlnesh Thal!REFACE this project report documents the EM!LOYEE MANAGEMENT SYSTEM. This is comprehensive application soItware that can maintain and handles all details oI the employee system used in any Iirm.
Авторское право:
Attribution Non-Commercial (BY-NC)
Доступные форматы
Скачайте в формате DOCX, PDF, TXT или читайте онлайн в Scribd
PR0}ECT REP0RT 0N ENPL0YEE NANAuENENT SYSTEN Submitteu foi BATABASE PR0}ECT
SUBMITTED TO SHAILENDRA VERMA
-SUBMTED BY
TARNDER SNGH VNESH PAL
1arlnder Slngh Anu vlnesh al ACKNOWLEDGEMENT
The satisIaction that accompanies that the successIul completion oI any task would be incomplete without the mention oI people whose ceaseless cooperation made it possible, whose constant guidance and encouragement crown all eIIorts with success. We are grateIul to our project guide Mrs. Shallendra verma Ior the guidance, inspiration and constructive suggestions that helpIul us in the preparation oI this project. We also thank our colleagues who have helped in successIul completion oI the project.
1arlnder Slngh Anu vlnesh al !REFACE This project report is submitted Ior the completion oI database management system project
This report documents the EM!LOYEE MANAGEMENT SYSTEM. This is comprehensive application soItware that can maintain and handles all details Ior the employee system used in any Iirm .
While developing this project, I was involved with system analysis, design and implementation process. This is a sample report describing in detail various aspects oI the system. I have used waterIall model Ior designing.
1arlnder Slngh Anu vlnesh al Introduction 1 !urpose:- The purpose oI this application are as Iollows : O The soItware is Ior automation oI employee management system. O It provides Iollowing Iacilities. 1. Search any employee`s detail 2. Advance search oI any employee consisting complex queries 3. Add a employee in the database with Iull details 4. Remove a employee Irom the database 5. Add project inIormation in to the database 6. Remove/ update project inIormation in to the database 7. Keep track oI all inIormation according to the departments 8. Update /Remove department inIormation Irom the database 9. Provide a user Iriendly graphical user interIace. 10. Provide inIormation regarding hours and salary, according to project, department, employee. Scope : The diIIerent areas where we can use this application are : a) 0Any education institute can make use this Ior educational purpose b) 0Any Iirm can use this to maintain inIormation about their employee , project and departments c) 0It can be used in oIIices and modiIications can be easily done according to requirements.
Technology Used : A. Concepts oI Database management system B. Concepts oI programming(visual C#) C. Concepts oI soItware engineering D. Visual studio 2010 E. SQL SERVER 2008 R2 F. SQL Quires
Assumptions 1. This application can be used as online application. 2. Customized data will be used in this application.
6 1arlnder Slngh Anu vlnesh al
Overview : Project is related to Employee management which is specially designed on the working principal oI a Iirm Ior managing employees. Employees details can be inserted, deleted, and updated accordingly
7 1arlnder Slngh Anu vlnesh al FeasibiIity Study The Ieasibility study is basically the test oI the proposed system in the light oI its workability, meeting user`s requirements, eIIective use oI resources and .oI course, the cost eIIectiveness. The main goal oI Ieasibility study is not to solve the problem but to achieve the scope. In the process oI Ieasibility study, the cost and beneIits are estimated with greater accuracy. Type of feasibilities: 1 Economic Feasibility Economic analysis is the most Irequently used technique Ior evaluating the eIIectiveness oI a proposed system. More commonly known as cost / beneIit analysis; in this procedure we determine the beneIits and savings that are expected Irom a proposed system and compare them with costs. We Iound the beneIits outweigh the costs; we take a decision to design and implement the new proposed system. Technical Feasibility This is concerned with speciIying equipment and soItware that will successIully satisIy the user requirement. The technical needs oI the system may vary considerably, but might include: The Iacility to produce outputs in a given time. Response time under certain conditions. Ability to process a certain volume oI transaction at a particular speed. Facility to communicate data to distant location. AIter examining technical Ieasibility, we give more importance to the conIiguration oI the system than the actual make oI hardware. The conIiguration gives the complete picture about the system's requirements: Ten to twelve workstations are required; these units should be interconnected through LAN so that they could operate and communicate smoothly. They should have enough speeds oI input and output to achieve a particular quality oI printing. Operational Feasibility
1arlnder Slngh Anu vlnesh al It is mainly related to human organizational and political aspects. The points to be considered are: What changes will be brought with the system? What organizational structures are disturbed? What new skills will be required? Do the existing staII members have these skills? II not, can they be trained in due course oI time? Generally project will not be rejected simply because oI operational inIeasibility but such considerations are likely to critically aIIect the nature and scope oI the eventual recommendations. For operational Ieasibility study we appointed a small group oI people who are Iamiliar with inIormation system techniques, who understand the parts oI the business that are relevant to the project and are skilled in system analysis and design process. 1. .
DRAWBACKS OF !RESENT SYSTEM Some oI the problems being Iaced in manual system are as Iollows: 1. All steps are time consuming. 2. Tracing a emplyee is diIIicult is very diIIicult and time consuming 3. Some inIormation data is not maintained. 4. There is no daily backup. 5. No central database can be created as inIormation is not available in database.
1arlnder Slngh Anu vlnesh al DATABASE ER DIAGRAM
10 1arlnder Slngh Anu vlnesh al
RELATIONAL DATABASE DEGIN BY ER DIAGRAM
11 1arlnder Slngh Anu vlnesh al
DECOMPOSITION INTO NORMALIZATION Degree oI normalization is 3 rd Normal Form
1arlnder Slngh Anu vlnesh al 1 {att2 == nu11 && att == nu11) att = " pnumber l1kL '" + text8ox7.1ext + "x' ", e1se att = " and pnumber l1kL '" + text8ox7.1ext + "x' ", qry = "se1ect pname, pnumber, p1ocaton,dnum,eeno,hours,mgeno 1rom department as d, proect as p, work_on as w where " + att + att + att2 + "and d.dnumber=p.dnum and w.pno=p.pnumber", getdatavew{), )
prvate vod text8ox6_1extChanged{obect sender, Lvent^rgs e) { 1 {att == nu11 && att == nu11) att2 = " p1ocaton l1kL '" + text8ox6.1ext + "x' ", e1se att2 = " and p1ocaton l1kL '" + text8ox6.1ext + "x' ", qry = "se1ect pname as 80JLC1_u^ML, pnumber, p1ocaton,dnum,eeno,hours,mgeno 1rom department as d, proect as p, work_on as w where " + att + att + att2 + "and d.dnumber=p.dnum and w.pno=p.pnumber", getdatavew{), )
prvate vod text8ox_1extChanged{obect sender, Lvent^rgs e) { 1 {att == nu11) att = " eeno l1kL '" + text8ox.1ext + "x' ", e1se att = " and eeno l1kL '" + text8ox.1ext + "x' ", qry = "se1ect eeno as LMl0YLL_u0,1name ^S I18S1_u^ML,hours ^S W08k1u6_u0u8S,pname as 80JLC1,pno 1rom emp1oyee as e, proect as p, work_on as w where " + att + att + "and e.eno=w.eeno and w.pno=p.pnumber", 6 1arlnder Slngh Anu vlnesh al getdatavew{), ) prvate vod text8ox_1extChanged{obect sender, Lvent^rgs e) { 1 {att == nu11) att = " pno l1kL '" + text8ox.1ext + "x' ", e1se att = " and pno l1kL '" + text8ox.1ext + "x' ", qry = "se1ect eeno as LMl0YLL_u0,1name ^S I18S1_u^ML,hours ^S W08k1u6_u0u8S,pname as 80JLC1,pno 1rom emp1oyee as e, proect as p, work_on as w where " + att + att + "and e.eno=w.eeno and w.pno=p.pnumber", getdatavew{), ) prvate vod button_C1ck{obect sender, Lvent^rgs e) { ths.C1ose{), ) prvate vod button_C1ck_{obect sender, Lvent^rgs e) { ^0v^uCL_SL^8Cu ad = new ^0v^uCL_SL^8Cu{css), ad.Show{),
) prvate vod text8ox_1extChanged{obect sender, Lvent^rgs e) { 1 {rado8uttonS.Checked == true) qry = "se1ect count{*) as u0_0I_L8S0u, sum{sa1ary) as SuM,max{sa1ary) as M^x1MuM_S^l^8Y,mn{sa1ary) as M1u1MuM_S^l^8Y 1rom emp1oyee where eno l1kL '"+text8ox.1ext+"x'", 1{rado8utton6.Checked==true) qry = "se1ect count{*) as u0_0I_L8S0u,sum{sa1ary) as SuM,max{sa1ary) as M^x1MuM_S^l^8Y,mn{sa1ary) as M1u1MuM_S^l^8Y 1rom emp1oyee where dno l1kL '" + text8ox.1ext + "x'", 1 {rado8utton7.Checked == true) qry = "se1ect count{*) as u0_0I_L8S0u,sum{sa1ary) as SuM,max{sa1ary) as M^x1MuM_S^l^8Y,mn{sa1ary) as M1u1MuM_S^l^8Y 1rom emp1oyee where sex l1kL '" + text8ox.1ext + "x'", 1 {rado8utton8.Checked == true) qry = "se1ect count{*) as u0_0I_L8S0u,sum{hours) as 101^l_W08k1u6_u0u8S,max{hours) as M^x1MuM_u0u8S,mn{hours) as M1u1MuM_u0u8S 1rom work_on where pno l1kL '" + text8ox.1ext + "x'", 1 {rado8utton.Checked == true) qry = "se1ect count{*) as u0_0I_L8S0u,sum{hours) as 101^l_W08k1u6_u0u8S,max{hours) as M^x1MuM_u0u8S,mn{hours) as M1u1MuM_u0u8S 1rom work_on where eeno l1kL '" + text8ox.1ext + "x'", 1 {rado8utton.Checked == true) qry = "se1ect count{*) as u0_0I_L8S0u,sum{hours) as 101^l_W08k1u6_u0u8S,max{hours) as M^x1MuM_u0u8S,mn{hours) as M1u1MuM_u0u8S 1rom work_on,proect where proect.dnum ='" + text8ox.1ext + "' and proect.pnumber=work_on.pno", 1 {rado8utton.Checked == true) qry = "se1ect count{*) as u0_0I_L8S0u,sum{hours) as 101^l_W08k1u6_u0u8S,max{hours) as M^x1MuM_u0u8S,mn{hours) as M1u1MuM_u0u8S 1rom work_on,emp1oyee where sex l1kL'" + text8ox.1ext + "x' and eeno=eno",
4 1arlnder Slngh Anu vlnesh al IM!LENETATION nardware requ|rement 2 Software requ|rement AfLer compleLlng Lhe packaglng process and produced dlsLrlbuLlon medla for Lhe appllcaLlon lL can run on a machlne LhaL has v8 prerequlslLe lnsLalled SiuwSie Requiiement: Hardware is the term given to machinery itselI and to various individual pieces oI equipment. It reIers to the physical de vices oI a computer system .Thus the input, storage, processing control and output devices are hardware.
MINIMUM HARDWARE REQUIREMENT: 1. Pentium Processor or above 2. Color Monitor 3. Keyboard 4. Minimum 8 GB Hard Disk 5. 32 MB RAM or above 6. 1.44 MB Floppy Disk Drive 7. 24 Mb Iree hard disk space plus additional space to hold
Software Requirement: SofLware means a collecLlon of program where Lhe ob[ecLlve ls Lo enhance Lhe capablllLles of Lhe hardware machlne 1he followlng paragraph deflnes Lhe sofLware of Lhe proposed sysLem developmenL M|n|mum software requ|rement Cperat|ng System Jlndows $000$p$vlsLa$wlndow 7 Language C # 010
44 1arlnder Slngh Anu vlnesh al
Future Scope FUTURE SCO!E OF A!!LICATION : This application can be easily implemented under various situations. We can add new Ieatures as and when we require. Reusability is possible as and when require in this application. There is Ilexibility in all the modules. SOFTWARE SCO!E:
Extensibility: This soItware is extendable in ways that its original developers may not expect. The Iollowing principles enhances extensibility like hide data structure, avoid traversing multiple links or methods, avoid case statements on object type and distinguish public and private operations.
Reusability: Reusability is possible as and when require in this application. We can update it next version. Reusable soItware reduces design, coding and testing cost by amortizing eIIort over several designs. Reducing the amount oI code also simpliIies understanding, which increases the likelihood that the code is correct. We Iollow up both types oI reusability: Sharing oI newly written code within a project and reuse oI previously written code on new projects.
Understandability: A method is understandable iI someone other than the creator oI the method can understand the code (as well as the creator aIter a time lapse). We use the method, which small and coherent helps to accomplish this.
Cost-effectiveness: Its cost is under the budget and make within given time period. It is desirable to aim Ior a system with a minimum cost subject to the condition that it must satisIy the entire requirement. Scope oI this document is to put down the requirements, clearly identiIying the inIormation needed by the user, the source oI the inIormation and outputs expected Irom the system.
4 1arlnder Slngh Anu vlnesh al
Conclusion From a proper analysis oI positive points and constraints on the component, it can be saIely concluded that the product is a highly eIIicient GUI based component. This application is working properly and meeting to all user requirements. This component can be easily plugged in many other systems.
Bibliography Books: 1 BEGNINING WITH VBNET THE COM!LETE REFERENCE VISUAL BASIC 6 !ROFESSIONAL VISAL BASIC
Internet: 1 !df worldcom Wikipediaorg Google Microsoftcom/vs/vb/ Vb internet help