HRMiS Report2

Human Resources Management System
PROJECT PROFILE
Project Title Organization Front End Back End Project Duration External Guidance Project Team Size Team
: : : : : : : :
Human Resources Management System Panamax infotech Ltd. Drive-in road, Ahmedabad Asp.Net with VB Microsift SQL Server 2005 50 Days Mr. Rahul Sharma 2 Persons Mehta Sachin (32), Saverdekar Ishan (102).
Dept of IT, HNGU.
Panamax InfoTech Limited
COMPANY PROFILE
Panamax InfoTech Limited (India) was incorporated in 2001. Panamax has been exemplifying all the sterling qualities of a successful enterprise .an integrated solutions provider which has bee able to achieve a perfect synergy of telecom, software, and back office solution.
It is involved in: Voice over IP Services & Solutions KPO engineering Services Information and Communication Technology Business solutions & Business Process Outsourcing Real Estate Finance
Why Panamax Infotech Limited? Panamax is one of the leading company in VoIP technology. They are also making software to make their work easy. In computer industry this company is growing with time. It has many partner companies across the glob. Thus It provides global atmosphere to trainee and give ones professional nourishment. Which of course makes deference in ones personality.
Dept of IT, HNGU.
INTRODUCTION
1.1 PROJECT SUMMARY
The Human Resources Management System is an online system for serving better way of managing employees, on hand projects, assigned work, to give satisfaction to the employee after their better work, managing comforts of employees that makes them work efficient, to have record of all financial and non-financial transaction of an employee on behalf of company, to have personal information of an employee and to manage it. Employee Interface: Human Resources Management System includes Administrative interface to facilitate employee for administrator related reporting and requesting works. It enables employee to make various kind of application, to view management information, administrators comments, approved and unapproved requests, staff manual policies, and pending payments. Administrative Interface: Human Resources Management System includes Administrative interface to manage employees personal information, Department, Designation, worked hour, on hand project, salary information as well it includes put remarks for each candidate for future reference. Departments information, its on hand job, capacity of work to be taken. Companys holidays and leave management modules, Incoming projects, Regular customers, etc.
1.2 PURPOSE
GOALS AND OBJECTIVE: Managing employees, project, client, determining capacity of company to
work up on such a project, hiring process, payment for work, and all from conducting interview to retirement of an employee all management with out any computer application is next to impossible. For managing such thing with an Intellectual machine HR MS is planned. Now-a-days Companies are working on a very practical strategy The more satisfactory employee get the more efficient he d work for company, which leads company to the sky heights. HR department Access this system to produce better result to work with employee. This system makes HR dept. work more efficient and easy for getting any information. HR MS is a complete solution to those who want to not get involved in such time wasting vein task.
Dept of IT, HNGU.
1.3 SCOPE
Human Resources Management System is for facilitate Human Resources Department to work efficient and deal with employee related problems. Companies now-a-days working on a strategy, that is Satisfied employee works more efficiently . For making them satisfied we have to fulfill their basic need, have to give them comfortable atmosphere to work, easy approach to administrators, and solve out all problems that employee faces while working. Purpose of Human Resources Management is same, to deal with all above, having record of work done by employee, reward them as per their work, record of on hand project, generate various report. It helps Human Resources Department to have record of employees, and to generate various report, and makes approach to administrator easy. Thus, Human Resources Management System enhances capability of Human Resources Department.
1.4 TECHNOLOGY & LITERATURE REVIEW

The technology used for the development of the system is ASP.NET. The .NET Framework The .NET Framework is a set of objects and blueprints from Microsoft for building applications. The .NET Framework provides the underlying functionality of ASP.NET. All applications developed under the .NET framework including ASP.NET applications, have certain key feature that ensure compatibility, security, and stability.
Common Language Runtime The Common Language Runtime (CLR) is an environment that manages the execution of code. In other words, it runs and maintains any code that you write. With the .NET framework and CLR you still write code and compile it. However, instead of compiling it into something that computer understands, you compile it into a language called the Microsoft Intermediate Language (MSIL). This language is shorthand way of representing all the code you have written. ASP.NET pages are compiled into MSIL as well. When you compile to MSIL, your application produces something called metadata. This is descriptive information about your application. It tells what the application can do,
Dept of IT, HNGU.
Human Resources Management System where it belongs, and so on.
Introduction about ASP.NET ASP.NET, the latest version of Active Server Pages, is Microsofts technology for building dynamic pages, database-driven Web sites. Active Server Pages is one of the most popular languages for building scalable, interactive Web sites. Several of the highest traffic Web sites on the Internet employs Active Server Pages. Examples include Dell Online, Barnes and Noble, 1-800-flowers, and the Microsoft site itself. ASP.Net represents a radical departure from previous versions of Active Server Pages.
Dept of IT, HNGU.
PROJECT MANAGEMENT
2.1 PROJECT PLANNING AND SCHEDULING
2.1.1 PROJECT PARADIGM / MODEL
INCREMENTAL MODEL
The Incremental Model combines elements of the linear sequential model with the iterative philosophy of prototyping. The incremental model applies linear sequences in a staged fashion as calendar time progresses. Each linear sequence produces a deliverable increment of the software. For example, word processing software developed using the incremental paradigm might deliver basic file management, editing and document production functions in the first increment; more sophisticated editing and document production capabilities in the second increment; spelling and grammar checking in the third increment; and advanced page layout capability in the fourth increment. It should be noted that the process flow for any increment can incorporate the prototyping paradigm.
Increment-1
System/Information Engineering Analysi Desig
Cod
Test
Delivery of 1st
Increment-2
Delivery of 2nd
Analysi
Desig
Cod Increment-3
Test
Delivery of 3rd
Analysi
Desig Cod Increment-4
Test
Delivery of 4th
Analysi
Desig
Cod
Test
Dept of IT, HNGU.
Calendar Time
INCREMENTAL MODEL
When an incremental model is used, the first increment is often a core product. That is, basic requirements are addressed, but many supplementary features remain undelivered. The core product is used by the customer. As a result of use and/or evaluation, a plan is developed for the next increment. The plan addresses the modification of the core product to better meet the needs of the customer and the delivery of additional features and functionality. This process is repeated following the delivery of each increment, until the complete product is produced. The Incremental process model, like prototyping and other evolution approaches, is iterative in nature. But unlike prototyping, the incremental model focuses on the delivery of an operational product with each increment. Early increments are stripped down versions of the final product, but they do provide capability that serves the user and also provide a platform for evaluation by the user. Software Requirements Analysis The requirements gathering process is intensified and focused specifically on software. Software requirements analysis encompasses understanding the information domain for the software as well as required function, behavior, performance, and interfacing. Requirements for both the system and the software are documented and reviewed with the customer. System/Information Engineering and Molding Software is a part of a larger system or business, work begins by establishing requirements for all system elements and then allocating some subset of these requirements to software.
Dept of IT, HNGU.
Human Resources Management System System engineering and analysis encompass requirements gathering at the system level with a small amount of top-level design and analysis Information engineering encompasses requirements gathering at the strategic business level and at the business area level. Design
Software design is a multi- step process that focuses on four distinct attributes of a program: data structure, software architecture, interface representations, and procedural details. The design process translates requirements into a representation of the software that can be assessed for quality before code generation begins. The design is documented and becomes part of the software configuration. Code Generation The design is translated into a machine readable form. If design is performed in a detailed manner, code generation can be accomplished mechanistically.
Testing The testing process focuses on the logical internals of the software, assuring that all statements have been tested, and on the functional externals i.e. conducting tests to uncover errors and ensure that defined input will produce actual results that agree with required results.
Maintenance Software maintenance applies to following phases in the existing program. Change in software due to errors. Change in software because the software must be adapted to accommodate changes in its external environment. Change in software when the customer requires functional or performance enhancements.
Dept of IT, HNGU.
Human Resources Management System 2.1.2 PROJECT PLAN After checking that project is feasible, project plan has been made by the project manager. Project plan consists of many different things. Such as:
Effort cost and time needed for the project. Require approach for the project Team management and scheduling.
Effort cost and time needed for the project: Project manager has to decide that how much
effort is needed for this project. According to cost is predicted in feasibility study he has to make cost estimation for the project. After deciding the cost and effort one has to take care of time management. The Project manager has decided the time and Effort as two team members and time of fifty days including the study of the system. Roles and Responsibilities: Role: I have joined the project as a trainee and for this project I have participated in development of the Human Resources Management System. Responsibilities: As a trainee and as a developer of this project my responsibility is to analysis, design and to implement a good system, which satisfy all the requirements and will give minimum no. of errors at the time of testing.
Dept of IT, HNGU.
Human Resources Management System 2.1.3 SCHEDULE REPRESENTATION Using the concept of Gantt chart Schedule chart is shown with specified month and week on which I had been working on the project. Work is shown in bars. Activity Days
Study User Require-ments and Under-stood the project in detail
May 2008 1 10 1 1 2 0 2 1 2 5 31 1 5 10
June 2008 15 16 17
Require-ment Analysis
DB Design Coding Testing Documen-tation
Dept of IT, HNGU.
10
2.2 RISK MANAGEMENT

2.2.1 RISK IDENTIFICATION Project Risk: Project Risks threaten the project plan. That is, if project risks become real, It is likely that project schedule will slip and that costs will increase. Project risks identify potential budgetary, schedule, personnel (staffing and organization), resource, stockholder, and requirements problems and their impact on a software project. Project complexity, size, and the degree of structural uncertainty were also defined as project risk factors. Technical Risks: Technical risks threaten the quality and timeliness of the software to be produced. If a technical risk becomes a reality, implementation may become difficult or impossible. Technical risks identify potential design, implementation, interface, verification, and maintenance problems. Business Risks: Business risks threaten the visibility of the software to be built. Business risks often jeopardize the project or the product. Candidates for the top five business risks are: Building an excellent product or system that no one really wants. Building a product that no longer fits into the overall business strategy for the company Building a product that the sales force doesnt under stand how to sell Losing the support of senior management due to a change in focus or a Change in people and Losing budgetary or personnel commitment. 2.2.2 RISK PLANNING: To assist the project team in developing a strategy for dealing with risk. An effective strategy must consider three issues: Risk Mitigating: Meet with current staff to determine causes for turnover Mitigate those causes that are under our control before the project starts. Once the project commences, assume turnover will occur and develop techniques to ensure continuity when people leave. Dept of IT, HNGU. Panamax InfoTech Limited 11 Risk avoidance. Risk monitoring. Risk management.
Human Resources Management System Organize project teams so that information about each development activity is widely dispersed. Define documentation standards and establish mechanisms to ensure that documents are developed in a timely manner. Assign a backup staff member for every critical technologist.
Risk Monitoring: General attitude of team members based on project pressures. The degree to which the team has jelled. Interpersonal relationships among team members. Potential problems with compensation and benefits. The availability of jobs within the company and outside it.
RMMM Plan: A risk management strategy can be included in the software project plan or the risk management steps can be organized into a separate Risk Mitigation, Monitoring and Management Plan. The RMMM plan documents all work performed as part of risk analysis and are used by the project manager as part of the overall project plan.
Dept of IT, HNGU.
12
SYSTEM REQUIREMENT STUDY (SRS)

3.1 USER CHARACTERISTICS
ORDINARY USERS: Here the registered users are considered as ordinary users. Here the users dont have the special access to modify any information. Here we can say ordinary user means employee, who are apply for various information, any special facility regarding on hand project, or can tell problem and risk factors of project in company. ADMINISTRATOR Administrator means they have all the right for insert / update / delete the records in database. Administrator has user name & password for access those rights. They review application and report from employee and access it. They deal to engage employees in deferent work. They look after employees work report and manages team of employees. They allows employee to have leave and provide feasible need for project which is requested
3.2 HARDWARE & SOFTWARE REQUIREMENT

HARDWARE REQUIREMENTS Pentium IV or Higher 10GB or More Hard Disk 256 RAM Internet/LAN Connection
SOFTWARE REQUIREMENTS Dept of IT, HNGU. O.S: Microsoft Windows 98/XP Package: Visual Studio.NET 2005 Tool: ASP.NET Database: SQL Server Designing Tools: MS VISIO, MS Paint, and PhotoShop. Reporting: MS Word Panamax InfoTech Limited 13
Human Resources Management System Web Design Tool: HTML
3.3 CONSTRAINTS
Hardware Limitations: The installation of Microsoft Visual Studio.NET requires that the RAM cannot be less than 128 MB and the processor cannot be less than 450 MHz speed as recommended in the Hardware Requirements. For fast access and operation 256 RAM should be there. Reliability Requirements: The main reliability requirement is the validation used. Without proper validation the system does not allow to enter that value into the database. For e.g. Every employee have to login. And E-mail address must have to contain @. Safety and Security Consideration: The highest level of security is assigned to the Panamax administrator who has all the rights to insert, edit and delete anything and everything. The rights given to the users are done by Panamax administrator only. And User also have to log-in to access system or any available feature.
Assumptions and Dependencies: Each and every records of this application has a unique identification number. All the access rights and permissions are given to the Administrator. No one can enter the system without having a login and password.
Dept of IT, HNGU.
14
SYSTEM ANALYSIS
4.1 STUDY OF CURRENT SYSTEM
The Current system is developed basically for Both Administrators and Users. This System is made in JSP as Front End and SQL Server 2000 as Back End. This System is works only as web application. The information provided to user would be as per their request and it would be timely and accurate. Thus accordingly usefully formatted information can be appended.
4.2 PROBLEM AND WEAKNESSES OF CURRENT SYSTEM

Each and every portion of the system is easily accessed by each person, if person is of less priority then also, so security of the system will lose. Current system is not flexible. If the The Current System has SQL Server 2000 as Back End so if number of records exceed after a certain limit it cannot be stored. Some features like project management and Travel management phases are not included in administrator system as well as in User system.
4.3 REQUIREMENTS OF NEW SYSTEM
4.3.1 FUNCTIONAL REQUIREMENT The Human Resources Management System is one type of client/Server side project. A user/admin can easily understand & operate. Administrator can add or modify current position of Jobs. Administrator can add list of various working days. Administrator can add or modify Clients information. User can access only certain modules titled Management information, Forms, Administrative information, Policies and staff Manual, Approval & comments, and alerts. Administrator distribute work to employees and get reports on it.
Dept of IT, HNGU.
15
Admin User: Administrator has all the rights for insert/update/delete. Employee User: He/She can make various application, report to administrator, view individual alerts, and Informational manuals.
4.3.2 OPERATIONAL REQUIREMENT Administrator: Administrator has user name & password. He/She has all the rights for insert/update/delete of each or all data, approving requests from Employee, work distribution, project management, keeping record of clients. Employee: Employee user are also password protected, they can apply their needs while working in company. They have to report, to higher authority, what they have worked. They can see alerts from administrator, working days of company, local news and staff manuals.
4.3.3 DATA REQUIREMENT 1. PRIVILEGED USERS (ADMINISTRATOR) INPUT DATA REQUIREMENTS: Following details are to be required by this category of users to become the member of association. User Name Password Re-Write Password Type Security Question Security Answer
OUTPUT DATA REQUIREMENTS: User will be required to get the user name and password to get all right for insert/update/delete.
Dept of IT, HNGU.
16
2. ORDINARY USERS (EMPLOYEE) INPUT DATA REQUIREMENTS: These users have deferent pages to access than administrator . They cannot use and access administrator pages. They will be given option for user id and password will be provided in envelopment, that later he/she can change. They have to just fill up certain details: Full Name Desired Id Telephone # Mailing Address Email Selection #
OUTPUT DATA REQUIREMENTS: Candidate selected as an employee will have to give above information and he ll be provided other information like his department, employee code, password, corporate id, designation, etc from administrator. 4.3.4 PERFORMANCE REQUIREMENT
The various performance requirements are described here: The system should display appropriate error message in case of bad handling on internal errors. The system should be user friendly and self explanatory. It should be easy to understand. Error handling of data and recovery of system should be easy enough for the user to understand the problems. The system should be able to handle the large the database if the amount of data entries increases. Maintaining database and its handling is a very important feature in maintaining the proper functioning of the system.
Dept of IT, HNGU.
17
4.3.5 SYSTEM SUPPORT REQUIREMENT
The System should be error free and easily modifiable. The maintenance does not require any special or specific tools. As the System is quite easily accessible and understandable, thus it is quite easy for the User training to be given at the installation of the System.
4.3.6 NON-FUNCTIONAL REQUIREMENTS
Our system is a very user friendly real time system. We offer best services in the form that it can be readable by any new user who is using the system for first time. It is very interactive, easy to use system. This system is very readable in the sense that any non-technical persons can also easily access this system with ease. A self-explanatory system with features like portability, testability is really a very user friendly real time system
Dept of IT, HNGU.
18
4.4 FEASIBILITY STUDY Feasibility is the measure of how beneficial or practical the development of any system in world. The
feasibility study involves following main criteria: Whether the identified user needs may be satisfied using current software and hardware technologies. The study will decide if the proposed system will be cost-effective and if it can be developed given existing budgetary constraints. Feasibility study should be cheap and quick. The result should inform the decision of whether to go ahead with a more detailed analysis.
FOUR TESTS FOR FEASIBILITY

1. OPERATIONAL FEASIBILITY: It is a measure of how well the solution will work in the Search world. It is also a measure of how people feel about the system/process. Operational feasibility is people oriented. 2. TECHNICAL FEASIBILITY: It is a measure of the practicality of specific technical solution and the availability of technical resources and expertise. Technical feasibility is computer oriented. 3. SCHEDULE FEASIBILITY: It is a measure of how reasonable the time taken in developing project? 4. ECONOMIC FEASIBILITY: It is a measure of the cost-effectiveness of a project or solution. This is often called a cost-benefit analysis. Economic feasibility deals with the costs and benefits of the information system.
Dept of IT, HNGU.
19
FEASIBILITY ANALYSIS OF Human Resources Management System 1. OPERATIONAL ANALYSIS: It is basically deals with how the system works. That is it keeps
track of both performance and efficiency. In our Site we have kept all things in mind while building the same. All aspects have been taken care of and thus we can say that performance wise it is good. It will measure the urgency of problem or the acceptability of solution. Performance: Information:
Economy:
Performance of Website is very excellent Project will help for administrator to manage various module and generate reports as per requested. If there is extra material required then we will provide. Our Project is totally user friendly with any user; also it is very easy for new user to handle it. And also it is totally security based. Our Project is working on any Web system without any error.
Control: Efficiency:
2. TECHNICAL ANALYSIS: In our Project, we have used ASP.NET as front end and SQL Server
as back end as mentioned. So performance wise we can say that ours is more efficient in the sense that it provides excellent GUI (Graphics User Interface). All the necessary resource like hardware and software available to build the system. Practically it is possible to implement it. IS THE PROPOSED SYSTEM PRACTICAL? The proposed system is definitely practical as we have all the resources available. Also building up this system requires the basic/ minimum amount of SRS that are easily available.
DO WE CURRENTLY POSSESS THE NECESSARY TECHNOLOGY? Looking into the SRS we can see that we posses all the hardware and software requirements. Also the technology used is easily available and deployed all around the world. DO WE POSSESS THE NECESSARY TECHNICAL EXPERTISE?
Dept of IT, HNGU.
20
Human Resources Management System Well, the system once developed can be easily handled by a non-technical person. So a technically sound expert is not required here. Hence this problem does not arise at all.
3. ECONOMIC ANALYSIS: It is an evaluation of development cost weighed against the ultimate

income is benefits derived from the developed system or product. Cost of resources that needed for development is less.
4. SCHEDULE ANALYSIS: it is deals with the deadline offered to complete the Website. The
procedure of submitting the project report at regular interval period are described in this project profile is fifty days so we completing our report and project within given time. So this totally in schedule feasible.
4.5 REQUIREMENTS VALIDATION

In this project we add validation criteria in all the different information some of them describe here. Login username & password for Administrator Must be requiring a same password and re-password for Administrator. If any field is compulsory and if that one is left blank then an error message will be displayed. Must be requiring a feel the home page. Contact No must be in 10 digits. The email id should contain the whole address i.e. address@sitename.com The name of the user should be character oriented, Etc.
Dept of IT, HNGU.
21
4.6 FUNCTION OF SYSTEM

4.6.1 SYSTEM FLOW
Dept of IT, HNGU.
22
USE CASES: Use Case Diagram is a generalized description of how a system will be used. It provides an overview of the intended functionality of the system. It is understandable by laymen as well as professionals. A use case is a set of scenarios that describing an interaction between a user and a system. A use case diagram displays the relationship among actors and use cases.
Add Project
Generate Timesheet Make Team Maintain the Database Put comments
Add Client
Add Employee
Administrator
Generate Reports
Add Leave & Holidays
Approve Requests
Fig.4.6 (a) Administrator use case diagram Fig.4.6 (b) GTO use case diagram View
Policies &
USECASE DIAGRAM (ADMINISTRATOR)

View
Management Info
Staff manual
Make Application
View Alerts
View Admin info
Pending Payment
View
Approval & comments
Employee
Maintain timesheet
Dept of IT, HNGU.

Fig.4.6 (c) Employee use case diagram
23
USECASE DIAGRAM (Employee)
4.7 DATA MODELING

4.7.1 DATA DICTIONARY Table Name:- Login Primary Key:-Username
Column Name Data Type Constrains
Type Username Password
nvarchar(15) nvarchar(15) nvarchar(15)
Not null Not null Not null
Table:- add_Client Primary Key:-Client code

Company_name Client_code Client_Name Client_Address Telephone_num Telephone2_num Fax_num Email URL
nvarchar(25) nvarchar(6) nvarchar(25) nvarchar(50) number(15) number(15) number(15) nvarchar(30) varchar(30)
Not null Not null Not null Null Not null Null Null Not null Null
Table:- add_Designation Primary Key:- Designation_code

Designation_code Designation_name Comment
nvarchar(15) nvarchar(15) nvarchar(50)
Not null Not null null
Table:- add_Dept Primary Key:- Dept_code

Dept of IT, HNGU.
24
Dept_code nvarchar(15) Dept_name nvarchar(15) Company_name nvarchar(25) Table:- add_staff Primary Key:-Employee_code Foreign Key:- Username,Designation_code,Dept_code Reference:- Login,add_dept,add_Designation.
Column Name Data Type
Constrains
Employee_code First_name Last_name Login_name Password Corp_E-mail DOB Joining_date Blood_group Permanent Location Designation_code Dept_code Reporting_to Address Pers_E-mail TelePhone_num Passport_numb
nvarchar(25) nvarchar(50) nvarchar(50) nvarchar(25) nvarchar(15) nvarchar(25) Date Date nvarchar(5) Boolean nvarchar(25) nvarchar(25) nvarchar(25) nvarchar(25) nvarchar(15) nvarchar(25) Number(15) Number(15)
Not null Not null Not null Not null Not null Not null Not null Null Null Not null Not null Not null Not null Null Not null null Not null null
Table:- add_holiday Primary Key:Column Name Data Type Constrains
H_date Description Location
Date nvarchar(50) nvarchar(25)
Table:-staff_resignation Foriegn Key:- Emp_code Reference: add_staff

Emp_code
nvarchar(15)
Not null
Dept of IT, HNGU.
25
Human Resources Management System Date_of_App Date_of_relieve Actual_Leaving_date Date Date Date Not null Not null Not null
Table:-standard_cost Foriegn Key:- Emp_code Reference: add_staff

Emp_code Date_of_costing Cost
nvarchar(15) Date Number(15)
Table:- Canteen_bill Foriegn Key:- Emp_code Reference: add_staff

Emp_code Payment_date Total_due Start_date
nvarchar(15) Date Number(15) Date
Not null Not null Not null Not null
Table:-Team Primary Key:-Team_code. Foriegn Key:- Lead_Emp_code, 1Emp_code, 2Emp_code, 3 Emp_code, 4 Emp_code, 5 Emp_code, 6 Emp_code, 7 Emp_code, 8 Emp_code, 9 Emp_code, 10 Emp_code. Reference: add_staff.
Team_code Lead_Emp_code 1Emp_code 2Emp_code 3Emp_code 4Emp_code 5Emp_code 6Emp_code 7Emp_code 8Emp_code 9Emp_code 10Emp_code
nvarchar(15) nvarchar(15) nvarchar(15) nvarchar(15) nvarchar(15) nvarchar(15) nvarchar(15) nvarchar(15) nvarchar(15) nvarchar(15) nvarchar(15) nvarchar(15)
Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null
Dept of IT, HNGU.
26
Table:- Add_project
Foreign Key:- Client_code, Team_code. Reference: add_client, Team.
Client_code Project_detail Project_name From_date To_date Description Location Team_code
nvarchar(15) nvarchar(150) nvarchar(15) Date Date nvarchar(150) nvarchar(15) nvarchar(15)
Not null Not null Not null Not null Not null Not null Not null Not null
Table:- Travel_info
Foreign Key:- Client_code, Emp_code, Dept_code. Reference: add_client, add_Dept, add_staff
Emp_code Dept_code Date_req From_date to_date client_comp Payment Adv_taken Client_code Project_name
nvarchar(15) nvarchar(15) Date Date Date boolean number(15) nvarchar(15) nvarchar(15) nvarchar(15)
Not null Not null Not null Not null Not null Not null Not null null null Not null
Table:- Timesheet
Foreign Key:- Emp_code. Reference: add_staff
Emp_code Date_report Hour1 Minute1
nvarchar(15) Date Int Int
Not null Not null Not null Not null
Dept of IT, HNGU.
27
Human Resources Management System Project_name Description nvarchar(15) nvarchar(50) Not null Null
4.8 FUNCTIONAL & BEHAVIORAL MODELING

4.8.1 CONTEXT DIAGRAM
CONTEXT DIAGRAM or DFD (LEVEL-0)
Dept of IT, HNGU.
28
4.8.2 First Level Data Flow Diagram
DATA FLOW DIAGRAM: Login (LEVEL-1)
Dept of IT, HNGU.
29
4.8.3 SECOND LEVEL DATA FLOW DIAGRAM
Data Flow Diagrams: Administrator(level-2)
Dept of IT, HNGU.
30
Data Flow Diagram: Employee(level-2)
Dept of IT, HNGU.
31
4.9 MAIN MODULES OF NEW SYSTEM

There are basically two modules in Human Resources Management System, Administrator and Candidate. Administrator: User: Management Information Application Forms Administrative Information Approval & comments Policies & staff Manual Pending Payments Alerts Project Information Leave Information Staff Information Travel Requisition Leave Approval Time sheet Information Library Management Laptop Management
4.10 SELECTION OF HARDWARE AND SOFTWARE & JUSTIFICATION

SOFTWARES: The soft wares selected for the Module are Microsoft Visual Web Developer 2005, SQL Server 2005, Micro Soft VISIO and Micro Soft Word.
Dept of IT, HNGU.
32
These soft wares have been selected for this module for the following reasons: Microsoft Visual Web Developer 2005 is selected and used because the System has been developed in ASP.Net and fro using ASP.Net Microsoft visual Web Developer 2005 is the most advanced and easy to use software with more functionality in it. SQL Server 2005 is used as Back End because in this software database are created very easily, it is very advanced and easy to use for create tables, views and store procedure etc. Micro Soft VISIO is used for drawing UML diagram. This soft ware made in Micro Soft so it is very easy to understand. We can draw all diagram perfect. Micro Soft Office is used for making reporting and presentation of the project.
HARDWARES: The hard wares selected for the development of the systems are: Pentium IV 500 MHz or higher 124 MB or higher RAM 10 GB or Higher Hard Disk Internet/LAN Connection
Dept of IT, HNGU.
33
SYSTEM DESIGN
5.1 DATABASE DESIGN/DATA STRUCTURE DESIGN
Design Approach:- All Software design methods share the same goal - to transform a set of data processing requirements into a computer program. The major objectives of the software design process are to document in sufficient detail the software design based on the software requirements and traceability to specifications. The output is complete, consistent, correct, testable and understandable information that can be used as input for code generation. The Functional Specifications and the system specifications are used as inputs for this process. The process ends when all the objectives of the software requirement document are met.
System Design:-
System Design is an important phase in which quality is
fostered in software development design is the process that actually transforms the requirements in to a finished software product (or) system. Design is the process of translating the requirement prepared during system study into design. The system design phase employs a variety of tools such as entity relationship diagram and so on. System design is primarily a synthesis function. In designing a new system one must have a clear picture of what is required and what must be done in order to achieve the requirement. Web pages are designed in such a way that it should be easily understandable for a layman.
Dept of IT, HNGU.
34
5.1.1 TABLES AND RELATIONSHIP
5.2 INPUT/OUTPUT & INTERFACE DESIGN
Dept of IT, HNGU.
35
Human Resources Management System 5.2.1 Designs Input Design:- Input Design is a part of overall system design which requires very care attention. If an error occurs in the input data then the result of that error may lead to unwanted problems. Errors committed by users can be controlled by a proper input design. Normally the data will be keyed into the system through the standard input device like keyboard. In such case, a validation program should be there to check the validity of the data. Output Design:- The output is the most important direct source of information to the user. Intelligent output Design will improve the systems relationship with the user and also helps in decision making, once the output requirement are determined, the system designer can decide, what to include in the system and how to structure it, so that the required output can be produced. Hence the output requirements are to be determined before going to actual system design. Output design is based on the following factors. Layout for the presentation of outputs. A simple and neat format is preferred rather than complex form of output.
Database Design:- Database design is the most critical part of the design phase. An elegantly designed, well-defined database can play as a strong foundation for the whole system. Database design transforms the information domain model created during the analysis into the data structures that will be required to implement the software system. The database used here is designed using SQL 2005. It is selected as it supports the .Net platform completely. It has very advanced security features which very essential while storing the data. All the tables are interconnected using primary and foreign key constrains. The tables are normalized and efforts are taken to remove any redundancy that might possibly occur.
5.2.2 ACCESS CONTROLS AND SECURITY Access Controls depends upon which type of user is using the system. The Administrator has all the rights and he is responsible to assign rights and roles to other users. The Administrator only has the rights over Setup Module where he can give rights to different users.
Dept of IT, HNGU.
36
Security is provided to the system by Login name and Password. Login Name and Password is assigned by Administrator to all users. Without this user cannot Login to the System.
5.3 SYSTEM ARCHITECTURE DESIGN

SYSTEM STRUCTURE OR HIERARCHICAL CHARTS
Login
Verify User
Administrator
Employee
Login Structure
Administrator
Dept of IT, HNGU. Add Various data
Panamax InfoTech Limited Generate Timesheet Put Alert & Comments

Generate Report Maintain Databas
37
Administrator Structure
Employee
View Policies & Staff manual
Make
Applicatio
View Alert & Employee Structure
View Approval
Maintain
Timeshee t
Dept of IT, HNGU.
38
IMPLEMENTATION PLANNING & DETAILS

Implementation includes all activities those take place to convert from old system to the new one. The new system may be totally new; replacing an existing manual or automated system, or it may be major modification to an existing system. In either case proper implementation is essential to provide a reliable system to meet organization requirements successful implementation but may not guarantee improvement in the organization using new system.
6.1 IMPLEMENTATION ENVIRONMENT

GUI:Microsoft Visual Web Developer 2005 provides GUI that is relatively easy to learn and use. This is a web based Application and almost all of the users are familiar with web systems and user with no computing experience can also learn to use the interface in a brief training session. The system is completely GUI. This is because today customer feels comfortable while working with images or pictures. As the project is web based, it can be used by any end-user. Thus user should feel convenient while working with the system. Thus system is user-friendly.
Multiple Users:
Dept of IT, HNGU.
39
Human Resources Management System Multiple users can use same form at same time without any lose of information. many of the users can access the same form at same time. There is no
performance problem and complain. Even the HRMS system is a centralized web based system. So
6.2 MODULE SPECIFICATION

In HRMS, basically there are two modules: Administrator Side and Candidate Side, Administrator: Administrator has all right for insert, update and delete the information. Administrative managers from the company can access this part of the web application. This section will be used to manage information of employee, projects, clients, off days, etc. Project Information Leave Information Staff Information Travel Requisition Leave Approval Time sheet Information Library Management Laptop Management Employee: Employee are users of this web application. Employee have to Log-in to access this system. They are given unique user id and password. They are enabled to access certain information and they can fill application forms and timesheet. Management Information Application Forms Administrative Information Dept of IT, HNGU. Panamax InfoTech Limited 40
Human Resources Management System Approval & comments Policies & staff Manual Pending Payments Alerts
6.3 SECURITY FEATURES

Security means protecting the data and programs against accidental or intentional destruction or disclosure to unauthorized person. The data and programs must be protected from theft, fire, disk corruption and other types of physical destruction. So we are using software called Visual SourceSafe, a Microsoft product. This software saves the whole program at the server. Only the team member can edit the program as they are given rights for particular program. No one other can edit the program.
6.4 CODING STANDARDS
The coding standard is the well-defined and standard style of coding. With the help of the coding standard any person can go into any code and figure out what's going on and new people can get up to speed quickly. A coding standard sets out standard ways of doing several things such as the way variables are to be named, the code is to be laid out, the comments are to be described, the work of function are to carried out etc.
We have used a 3-tier architecture coding in our system.
Three-Tier Client Server Model:
Dept of IT, HNGU.
41
The limited effectiveness of two-tier client/server solutions ushered in an improved model for client/server development. The three-tier client/server model is based on the capability to build portioned applications. Portioning an application breaks up your code into logical components. The service model suggests that these components can be logically grouped into three tiers : user services, business services, and data services. After an application has been developed by using this model and technique, each component can then be deployed to whichever machine will provide the best performance, depending on your situation and the current business need. Figure shows a physical implementation of the three-tier client/server model. The following benefits illustrate the value of distributed three-tier client/server development:
Reuse:
The time you invest in designing and implementing components is not wasted because you can share then among applications.
Performance:
Because you can deploy your components on machines other than the client workstation. You have the ability to shift processing load from a client machine that might be underpowered to a server with extra horsepower. This flexibility in deployment and design enables you, as a developer, to take advantage of the best possible methods for each aspect of your applications execution, and results in better performance.
Manageability:
Encapsulation of your applications services into components enables you to break down large, complex applications into more manageable pieces.
Maintenance:
The centralization of components for reuse has an added benefit. They become easier to redeploy when modifications are made, thus keeping pace with business needs.
Dept of IT, HNGU.
42
Dept of IT, HNGU.
43
Three-Tier client/server physical implementation
Dept of IT, HNGU.
44
TESTING
7.1 TESTING PLAN
The main objective of doing testing is to identify all defects existing in software. Basically the testing of software consists of providing the program with a set of test inputs (test case) and observing that whether the software behaves as expected.
Testing is the process of executing a program with the explicit intention of finding errors, which makes the program fail. The tester is actually trying to make the program fail. A successful test is the one that finds errors.
Regardless of which strategies the analysts follow, there are preferred practices to ensure that the testing is useful. The levels of tests and types of test data, combined with testing libraries are important aspects of the actual test process. Among the various testing practices or strategies that are followed by analysts, the two important ones are unit testing and system testing.
PRINCIPLES Following are the testing principles, which are used, All tests should be traceable to user requirements. Tests should be planned long before testing begins. Testing should begin in small and progress toward testing in the large. Exhaustive testing is not possible. To be most effective testing should be conducted by an independent third party.
Dept of IT, HNGU.
45
7.2 TESTING STRATEGY

Unit Testing Module Testing In this testing individual components and modules are tested to ensure that they operate correctly. I have tested each and every module such as Login, Home page, Setup Module which has Sub modules like Facility, Area, Building, etc. For these I have checked that Edit, Delete is done in database which reflects correctly in front end and for Condition Assessment Photos and Cad are uploaded properly.
Integration Testing This testing is a systematic technique for constructing the program structure while at the same time conducting tests to uncover errors associated with interfacing. All the modules testing in the unit testing are integrated and are tested for their inter-dependency. This system mainly works on the integration of all the departments. So I have checked when the Client is logged out then it should not be displayed in Client List page
Security Testing This testing is done to confirm that the software allow only authorized users to access and use the system. There are two types of users in this system. I have tested entering the user name and password for all types of Users. Like only administrator has the right to access the Setup Module. Employee has only rights to view alerts, comments, manuals, current projects, his profile and generated reports and fill application forms and time sheet.
Acceptance Testing This type of testing is done when the system is being deployed. There are fifteen modules out of which six are completed and after that the acceptance testing will come into picture.
Human Factor Testing If administrator wants to add any record then he has to enter some compulsory fields and then click on submit. If he do not select enter compulsory fields and click on submit then an alert message will pop up saying Enter ***** field.
Dept of IT, HNGU.
46
Human Resources Management System User can upload Photos, Cads so if the user uploads by mistake any other file like text file or any other file then a message will be there saying that You can upload only jpeg, gif, etc files only.
Black Box Testing Strategy Black Box Testing is not a type of testing; it instead is a testing strategy, which does not need any knowledge of internal design or code etc. As the name "black box" suggests, no knowledge of internal logic or code structure is required. The types of testing under this strategy are totally based/focused on the testing for requirements and functionality of the work product/software application. Black box testing is sometimes also called as "Opaque Testing", "Functional/Behavioral Testing" and "Closed Box Testing". The base of the Black box testing strategy lies in the selection of appropriate data as per functionality and testing it against the functional specifications in order to check for normal and abnormal behavior of the system. Now a days, it is becoming common to route the Testing work to a third party as the developer of the system knows too much of the internal logic and coding of the system, which makes it unfit to test the application by the developer. In order to implement Black Box Testing Strategy, the tester is needed to be thorough with the requirement specifications of the system and as a user, should know, how the system should behave in response to the particular action. us testing types that fall under the Black Box Testing strategy are: functional testing, stress testing, recovery testing, volume testing, User Acceptance Testing (also known as UAT), system testing, Sanity or Smoke testing, load testing, Usability testing, Exploratory testing, adhoc testing, alpha testing, beta testing etc.
White Box Testing Strategy White box testing strategy deals with the internal logic and structure of the code. White box testing is also called as glass, structural, open box or clears box testing. The tests written based on the white box testing strategy incorporate coverage of the code written, branches, paths, statements and internal logic of the code etc.
Dept of IT, HNGU.
47
In order to implement white box testing, the tester has to deal with the code and hence is needed to possess knowledge of coding and logic i.e. internal working of the code. White box test also needs the tester to look into the code and find out which unit/statement/chunk of the code is malfunctioning.
Bottom-up Testing Bottom-up testing tests the lower level of a system before testing its higher-level components.
Field Wise Testing

(Level1)
Form Wise Testing

(Level2)
Form Integration Testing

(Level3)
System Testing
(Level4) (Testing Sequence)
At first level, we check out the fields of the form and also test the validation of the data. There are some fields that took data automatically from the existing database. At second level, we test forms of the system. These forms are working properly. At third level, we test the integration of the different forms. It retrieves data in proper manner. It also takes the data in correct format and stores it.
7.3 TESTING METHODS

Software Testing involves executing an implementation of the software with test data and examining the outputs of the software and its operational behavior to check that it is performing as required. Statistical Testing
Dept of IT, HNGU.
48
Human Resources Management System Statistical Testing is used to test the programs performance and reliability and to check how it works under operational conditions. Tests are designed to reflect the actual user inputs and their frequency. The stages involved in the static analysis for this system are follows. Control flow analysis Unreachable code Unconditional branches into loops Data use analysis Variable used before initialization Variables declared but never used Variables assigned twice but never used between assignments Possible array bound violations Declared variables Interface analysis Parameter type mismatches Parameter number mismatches Non-usage of the results of functions Uncalled functions and procedures Storage management faults Images not Stored in Resources Insufficient memory space
Performance Testing
Performance testing is designed to test the runtime performance of the system within the context of the system. These tests Developer performed as module level as Developer as system level. Individual modules Developers tested for required performance.
Dept of IT, HNGU.
49
Condition Testing
Condition testing is a test case design method that exercises the logical conditions contained in a program module. If the condition is incorrect, then as least one part of the condition is incorrect. It may include Boolean variable error String Index out of Bound error Null Pointer Assignment Input Output Connection Exceptions Images or Map Unloaded errors Arithmetic expression error
Interface Testing Interface testing is integral part of Integration testing. Therefore Developer checked for the following: Interface misuse Interface misunderstanding Developer examined the code to be tested and explicitly list each call to an external component. In the system, standards tests for GUIs have been performed, which are as follows. The position and related labels for all controls checked. All menu functions and sub functions verified for correctness. Validations for all inputs done. Each menu functions tested, whether it invokes the corresponding functionality properly. Pull down controls was verified for proper functionality. Whether the non-editable text control is disabling and it was also verified that it doesnt exceed the maximum length. Whether the system prompts the user with appropriate message as and when invalid information is entered.
Dept of IT, HNGU.
50
Human Resources Management System All required fields arent left blank Object Testing Object testing is to test object as individual components, which are often larger than single function. Here following activities have taken place. Testing the individual operations associated with object. Testing individual object classes. Testing cluster of objects Testing object-oriented system. Now we will discuss how testing and debugging is done of this application. Our application can be divided into parts like: Values of some attributes of forms are coming from database so no chance of wrong selection of that. To make queries to database and retrieve information from it. Maintain databases such that its accessing speed becomes fast. Reduce memory requirements for the database. Maintain proper integration among database. 1) White Box Testing
Internal Working Input Output
It is performed to reveal the problems related to the internal structure of the program. This requires that the tester should have the detailed knowledge about the internal structure of the program. A common goal of white-box testing is to ensure a test exercises covering every path through a program. A fundamental strength that all white box testing strategies share is that the entire software implementation is taken in to account during testing, which facilitates error detection even when the requirement Dept of IT, HNGU. Panamax InfoTech Limited 51
Human Resources Management System specification is vague or incomplete. The effectiveness or thoroughness of white-box testing is commonly expressed in terms of test or code coverage metrics, which measure the fraction of code exercised by test cases. Control-flow testing, loop testing, and data-flow testing, all maps the corresponding flow structure of the software into a directed graph. Test cases are carefully selected based on the criterion that all the nodes or paths are covered or traversed at least once. By doing so we may discover unnecessary "dead" code -code that is of no use, or never get executed at all, which cannot be discovered by functional testing. Some of the white-box testing techniques are: 2) Black-box Testing:
Input
Output
The black-box approach is a testing method in which test data are derived from the specified functional requirements without regard to the final program structure. It is also termed data-driven, input/output driven or requirements-based testing. Because only the functionality of the software module is of concern, black-box testing also mainly refers to functional testing -- a testing method emphasized on executing the functions and examination of their input and output data The tester treats the software under test as a black box -- only the inputs, outputs and specification are visible, and the functionality is determined by observing the outputs to corresponding inputs. In testing, various inputs are exercised and the outputs are compared against specification to validate the correctness. All test cases are derived from the specification. No implementation details of the code are considered. It is obvious that the more we have covered in the input space, the more problems we will find and therefore we will be more confident about the quality of the software. Ideally we would be tempted to exhaustively test the input space. But exhaustively testing the combinations of valid inputs will be impossible for most of the programs, let alone considering invalid inputs, timing, sequence, and resource variables. Combinatorial explosion is the major roadblock in functional testing. To make things worse, we can never be sure whether the specification is either correct or complete. Due to limitations of the language used in the specifications (usually natural language), ambiguity is often inevitable. Even if we
Dept of IT, HNGU.
52
Human Resources Management System use some type of formal or restricted language, we may still fail to write down all the possible cases in the specification.
The research in black box testing mainly focuses on how to maximize the effectiveness of testing with minimum cost, usually the number of test cases. It is not possible to exhaust the input space, but it is possible to exhaustively test a subset of the input space. Partitioning is one of the common techniques. If we have partitioned the input space and assume all the input values in a partition is equivalent, then we only need to test one representative value in each partition to sufficiently cover the whole input space. Domain testing partitions the input domain into regions, and considers the input values in each domain an equivalent class. Domains can be exhaustively tested and covered by selecting a representative value(s) in each domain. Boundary values are of special interest. Experience shows that test cases that explore boundary conditions have a higher payoff than test cases that do not. Boundary value analysis requires one or more boundary values selected as representative test cases. The difficulties with domain testing are that incorrect domain definitions in the specification cannot be efficiently discovered. This testing was done with dummy data created by us Specifications: - In this type of testing first of all we have to compare the requirement specification along with existing system to see whether actual requirement is satisfied or not. Navigation: - secondly, how system works and how you will navigate the entire the system. I.e. System navigation flow that should be clear. Field size & validity: - It determines size of the field and any validation like whether field is mandatory or not. Some of the fields have alphabets only such as name field. Here only alphabets must be allowed. Font size & type: - Testing is necessary for form layout .it describe type of font and size of font and Test whether each of font are placed at right place as desire or not. Alignment: - In the form level design to set the alignment are derived and covered all field with it views and justification of the field with set alignment. Add, Modify, Delete (Storage): - After completion of all the types of above mentioned testing types, carry out the testing for add, modify, Delete functionality of system. Here you have to test whether you can add the data in database modify the data in database and delete the data from the database.
Dept of IT, HNGU.
53
Human Resources Management System Black-box testing attempts to find errors in the following Categories: Incorrect or missing function. Interface errors. Errors in fetching external data. Behavior or performance errors. Initialization and termination error.
7.4 TEST CASES

Purpose Login into the system Adding new Requirement Valid username and password Expected Result Identify the user and give the
rights according to the user users, All the valid input and the rights Adds or edits the users
Editing by the admin and roles to particular user rights and roles in the table Adding, Editing All the valid details required for Adds or edits the Position Positions by Admin Access to adding a Facility and display in the List of Position. whole Input all forms required to be Adds or edits the details in various tables of Database. As per as decided and
database by Admin checked by filling information Layout in different kind Deferent kind of systems.
of systems designed. Validation in telephone Valid telephone number less then Adds or edits information if numbers address and e-mail 13 digit and email address it is valid. containing @.
SCREEN SHORTS & USER MANUAL
Dept of IT, HNGU.
54
SCREEN SHORTS
Login.aspx
Forgot Password.aspx
Dept of IT, HNGU.
55
Forgot password.aspx
Dept of IT, HNGU. Panamax InfoTech Limited 56
Change_password.aspx
Second_Page.aspx
Dept of IT, HNGU.
58
Add_pro.aspx
Previous_pro.aspx
Dept of IT, HNGU.
60
Add_client.aspx
Add_leave.aspx
Dept of IT, HNGU.
62
Leave_report.aspx
Dept of IT, HNGU.
63
Add_holiday.aspx
Holiday_List.aspx
Dept of IT, HNGU.
65
Add_comp_off.aspx
Dept of IT, HNGU.
66
Admin_online_leave.aspx
Add_dept.aspx
Add_Design.aspx
Dept of IT, HNGU.
69
Add_staff.aspx
Dept of IT, HNGU.
70
Dept of IT, HNGU.
71
Add_Travel.aspx
Dept of IT, HNGU.
72
Travel_report.aspx
Dept of IT, HNGU.
73
Travel Exp Input.aspx
Dept of IT, HNGU.
74
TravelExpReport.aspx
Dept of IT, HNGU.
75
Timesheet.aspx
Dept of IT, HNGU.
76
Timesheet Report.aspx
Dept of IT, HNGU.
77
Staff_Resignation.aspx
Dept of IT, HNGU.
78
Staff_directory.aspx
Dept of IT, HNGU.
79
Ex_Employee.aspx
Dept of IT, HNGU.
80
USER MANUAL ASP.NET 2.0
Microsoft ASP.NET 2.0 is revolutionary in the way it increases productivity. The Primary Goal of ASP.NET 2.0 is to enable you to build powerful, secure, and dynamic applications using the least possible amount of code. Goals of ASP.NET 2.0 ASP.NET 2.0 is a major release of the of the product and an integral part of the .NET Framework 2.0. This release of the Framework was code-named Whidbey internally at Microsoft. ASP.NET 2.0 heralds a new wave of development that should eliminate any of the remaining barriers to adopting this new way of coding Web applications. Developer Productivity
Dept of IT, HNGU.
81
One Goal the development team had for ASP.NET 2.0 was to eliminate much of the tedious coding that ASP.NET 2.0 originally required and to make common ASP.NET task easier. The ASP.NET team developing ASP.NET 2.0 had the goal of reducing by two-thirds the number of lines of code required for an ASP.NET application. For that you have to include only some server controls: one control to get data and oe control to display data. Then the controls are wired together.
Performance and Scalability One of Goals for ASP.NET 2.0 set by the Microsoft team was to provide the worlds fastest Web application server. One of the most exciting performance enhancements is the new caching capability aimed at exploiting Microsoft SQL Server. ASP.NET now includes a feature called SQL cache invalidation. Before ASP.NET 2.0, it was possible to cache the results that came from SQL Server and to update the cache based on a time interval. Another big area of change in ASP.NET is in the area of performance and scalability.ASP.NET 2.0 now provides 64-bit support. This means you can noe run your ASP.NET applications on 64-bit Intel or AMD processors. Overview of the .NET Framework The .NET Framework consists of the platform and tools needed to develop and deploy .NET applications. It includes an execution environment for .NET programs (the Common Language Runtime, or CLR for short), prewritten services that programs can access from this environment (the .NET Runtime classes), and the development tools to produce such programs (VS.NET).
Dept of IT, HNGU.
82
Unlike traditional Windows applications, .NET applications are not compiled to native machine code but are compiled to interpreted code called Microsoft Intermediate Language (IL). IL code is the inherent language of the CLR, which is similar to a Java VM, acting as an operating system on the operating system, interpreting the IL code in real time. Since IL code is interpreted, responsibilities such as memory allocation and exception handling become property of the CLR and not the programmer. For this reason, IL code is referred to as managed code, whereas native machine code is said to be unmanaged. One of the compelling reasons to develop applications in the .NET Framework is the .NET Runtime class. Similar to the Java Class Libraries, these classes are the building blocks for writing .NET applications. Common Language Runtime The common language runtime (CLR) is responsible for run-time services such as language integration, security enforcement, and memory, process, and thread management.
Dept of IT, HNGU.
83
Human Resources Management System Class Libraries Base classes provide standard functionality such as input/output, string manipulation, security management, network communications; thread management, text management, and user interface design features. The ADO.NET classes enable developers to interact with data accessed in the form of XML through the OLE DB, ODBC, Oracle, and SQL Server interfaces. XML classes enable XML manipulation, searching, and translations. The ASP.NET classes support the development of Web-based applications and Web services. The Windows Forms classes support the development of desktop-based smart client applications.
The Common Type System specifies the types supported by the CLR. The types specified by the CLR include ClassesThe definition of what will become an object; includes properties, methods, and events InterfacesThe definition of the functionality a class can implement, but does not contain any implementation code Value TypesUser-defined data types that are passed by value DelegatesSimilar to function pointers in C++, delegates are often used for event handling and callbacks The type system sets out the rules that language compilers must follow to produce code that is crosslanguage compatible.
Dept of IT, HNGU.
84
ADO.NET
As its name suggests, ADO.NET is Microsofts ActiveX Data Object (ADO) model for the .NET Framework. ADO.NET is not simply the migration of the popular ADO model to the managed environment but a completely new paradigm for data access and manipulation. Unlike ADO, ADO.NET is intended specifically for developing web applications. This is evident from its two major design principles: Disconnected DatasetsIn ADO.NET, almost all data manipulation is done outside the context of an open database connection. Data is read into an entity called a Dataset and the database is immediately closed. Operations (update/insert/delete) are performed against the Dataset as required. When the database is ready to be updated, it is reopened and data is imported from the Dataset.
Dept of IT, HNGU.
85
Human Resources Management System Effortless Data Exchange with XMLDatasets can converse in the universal data format of the Web, namely XML. A Dataset can export its contents to XML, or import data in XML format. One is no longer restricted to exchanging data in proprietary COM format. This is especially important in the Internets heterogeneous environment, where one may want to interoperate with non-Windows machines that lack support for COM. ADO. Nets disconnected methodology leads to the natural division of its object model into two layers, the Managed Provider, which actually communicates with the database, and the disconnected Dataset, which performs the desired data manipulation. These entities communicate to each other using a Managed Providers Data Adapter object, as illustrated in the ADO.NET model in Figure .
ADO.NET Model
From Figure, we can see that the Dataset is the object that glues the ADO.NET Framework together, acting as a bridge between relational databases and the world of XML. The role of the Dataset as a mediator between these domains is significant, because it frees developers from having to represent their data in only one of these formats.
Dept of IT, HNGU.
86
Human Resources Management System With ADO.NET, one can take relational data and view it as hierarchical XML, so it can be utilized by XML parsers and XML technologies. At the same time, one can take XML data and persist it to an SQL database. SCHEMA A schema is an XML document that describes the structures, constraints, and relationships of an XML data file. Since a schema is itself an XML document, it can be embedded in the XML data file that it depicts. Schemas are an important concept, because of the intrinsic XML support in ADO.NET. The relationships expressed in an XML schema can be imported and enforced by a Dataset. Similarly, a Dataset can export its constraints and relationships to an XML schema. DATASETS ADO.NET is centered on the Dataset object. Using it together with the Data Adapter object of a Managed Provider, one can manipulate data outside the context of an open database connection. Think of a Data Adapter as a messenger that ferries information from the database to the Dataset and vice versa. A Data Adapter is not the only way a Dataset can obtain dataXML is also a viable source and target. Datasets can read XML, and can make them available as XML to other clients. This is a significant feature; it means that developers can move data seamlessly between proprietary databases and universal XML. Examples that follow will explore the role of XML in the ADO.NET Framework. Unlike a Record set, a Dataset can house multiple tables and the relations between them. If the database has constraints (perhaps the combination of two fields must be unique), a Dataset can enforce this restriction. It is thus more accurate to think of a Dataset as a lightweight in-memory database (as opposed to a Record set, which contains no relational information regarding the data it contains). Because a Dataset can house multiple tables, it exposes a collection of Data Table classes. These in turn expose Data Row and Data Column collections, representing the records and fields in the table(s). Dept of IT, HNGU. Panamax InfoTech Limited 87
ADO.NET ARCHITECTURE Microsoft ADO. Nets object model encompasses two distinct groups of classes: content components and managed-provider components. The content components include the Dataset class and other supporting classes such as Data Table, Data Row, Data Column, and Data Relation. These classes contain the actual content of a data exchange. The managed-provider components assist in data retrievals and updates. Developers can use the connection, command, and data reader objects to directly manipulate data. In more typical scenarios, developers use the Data Adapter class as the conduit to move data between the data store and the content components. The data can be actual rows from a database or any other form of data, such as an XML file or an Excel spreadsheet. ADO developers should have no problems understanding connection and command objects. A data reader is a new object providing fast, forward-only, and read-only access to data. This is similar to an ADO Record set with server-side, forward-only, and read-only cursor types. ADO.NET BENEFITS ADO.NET brings with it a number of benefits, which fall into the following categories: Interoperability The ability to communicate across heterogeneous environments. Scalability In a client/server model, it is typical for a client to acquire and hold on to a connection to the server until all requests are fulfilled. While this works fine in small- to medium -scale applications, this solution is not scalable across a large enterprise.
Dept of IT, HNGU.
88
Human Resources Management System As soon as the number of clients reaches a certain threshold, the server becomes the bottleneck as database connections eat up network and CPU resources. ADO.NET automatically keeps connections to a data source in a pool, so when an application thinks it is tearing down a connection; it's actually returning it to the resource pool. This allows connections to be reused, avoiding the cost of reconstructing new connections from scratch. Working with data in this disconnected fashion is not new to ADO programmers. The disconnected record set was introduced in early versions of ADO. However, in ADO, it is up to the developer to implement this feature, whereas in ADO.NET, data is disconnected by nature. Productivity ADO. Nets rich framework classes allow developers to boost their productivity. Current ADO developers should have no problems getting up to speed with the object model, because ADO.NET is a natural evolution of ADO. The core functionality remains the same. We still have the connection object, representing the pipeline through which commands are executed. With ADO.NET, the functionality is factored and distributed to each object in the modelmuch better than in previous versions of ADO. In short, ADO.NET improves developers' productivity through its rich and extensible framework classes. These features are complemented by the rich toolsets for ADO.NET in Visual Studio.NET, which enable rapid application development. Performance Because ADO.NET is mainly about disconnected datasets, the system benefits from improved performance and scalability. The database server is no longer a bottleneck when the number of connection requests goes up. Managed Providers in ADO.NET also enable implicit connection pooling, which reduces the time required to open a connection. Previous marshaling of record sets required type conversion to make sure that the data types were all COM based.
Dept of IT, HNGU.
89
Human Resources Management System Since the disconnected dataset is in XML format, there is no need for this type conversion during transport, as opposed to how data in Network Data Representation format must be dealt with. DATASET If you are familiar with ADO, you know that data transfers between components are a record set. The record set contains data in a tabular form. Whether the record set includes information from one or many tables in the database, the data is still returned in the form of rows and columns as if they were from a single table. ADO.NET allows for more than just a record set to be shared between application components. This is one of the most important features of ADO.NET: we will be transferring a Data Set instead of a record set. The Data Set can be viewed as an in-memory view of the database. It can contain multiple Data Table and Data Relation objects. With previous versions of ADO, the closest you could get to this functionality was to exchange data with a chain of Record set objects. When the client application receives this chained record set, it can get to each of the record sets through NextRecordset ( ); however, there is no way to describe the relationship between each of the record sets in the chain. Since a Data Set is disconnected, it must provide a way to track changes to itself. The Data Set object provides a number of methods so that all data manipulation done to the DataSet can be easily reconciled with the actual database (or other data source) at a later time. They include: Has Changes ( ), Has Errors, Get Changes ( ), Accept Changes ( ), and Reject Changes ( ). You can employ these methods to check for changes that have happened to the Data Set, obtain the modifications in the form of a changed Data Set, inspect the changes for errors, and then accept or reject the changes. If you want to communicate the changes to the data store back end (which is usually the case), just ask the Data Set for an update. The Data Set is intended to benefit enterprise web applications, which are disconnected by nature. You don't know that the data at the back end has changed until you have updated records you were editing or performed any other tasks that required data reconciliation with the database. Dept of IT, HNGU. Panamax InfoTech Limited 90
A Data Set contains two important collections. The first is the Tables (of type DataTableCollection), which holds a collection for all the tables belonging to a given Data Set. The second collection contains all the relationships between the tables, and it is appropriately named the Relations (of type DataRelationCollection). DATATABLE Data Table represents a table of data and thus contains a collection of Data Columns as a Columns property and a collection of Data Rows as a Rows property. The Columns property provides the structure of the table, while the Rows property provides access to actual row data. Fields in the table are represented as Data Column objects, and table records are represented as Data Row objects. Here is some sample code that dumps the name of each column as a row of headers, followed by each row of data DATAVIEW The Data View object is similar to a view in conventional database programming. We can create different customized views of a Data Table, each having different sorting and filtering criteria. Through these different views, we can traverse, search, and edit individual records. This ADO.NET concept is the closest to the old ADO record set. In ADO.NET, Data View serves another important role data binding to Windows Forms and Web Forms. DATA RELATION A Data Set object as a collection of Data Table objects alone is not useful enough. A collection of Data Table objects returned by a server component provides little improvement upon the chained record set in previous versions of ADO. In order for your client application to make the most of the returned tables, you also need to return the relations between these Data Tables. This is where the Data Relation object comes into play. THE DATA READER OBJECT
Dept of IT, HNGU.
91
Human Resources Management System The data reader is a brand new concept to ADO developers, but it is straightforward. A data reader is similar to a stream object in object-oriented programming (OOP). If you need to access records in a forward-only, sequential order, use a data reader because it is very efficient. Since this is a server side cursor, the connection to the server is open throughout the reading of data. THE DATA ADAPTER OBJECT Along with the introduction of data reader, ADO.NET also brings the Data Adapter object, which acts as the bridge between the data source and the disconnected Data Set. It contains a connection and a number of commands for retrieving the data from the data store into one Data Table in the Data Set and updating the data in the data store with the changes currently cached in the Data Set. Even though each Data Adapter maps only one Data Table in the Data Set, you can have multiple adapters to fill the Data Set object with multiple Data Tables. Both OleDbDataAdapter and SqlDataAdapter are derived from DbDataAdapter, which in is in turn derived from Data Adapter abstract class. This Data Adapter abstract class implements the IDataAdapter interface, which specifies that it supports Fill and Update. IDataAdapter is specified in the System. Data namespace, as is the Data set itself.
Dept of IT, HNGU.
92
SQL SERVER 2005 EXPRESS EDITION
SQL Server Express is a free and easy-to-use database product that is based on SQL Server 2005 technology. It is designed to provide a database platform that offers superior ease of use, enabling fast deployments for its target scenarios. The ease of use starts with a simple and robust graphical user interface (GUI) setup that guides the user through the installation process. The GUI tools that come for free with SQL Server Express include SQL Server Management Studio Express Edition (Technical Preview version available at launch), Surface Area Configuration Tool, and SQL Server Configuration Manager. These tools simplify the basic database operations. The design and development of database applications are made easier by the integration with Visual Studio projects. In addition, I introduce the ability to deploy database applications by moving them like typical Windows files. The servicing and patching are also simplified and automated.
Dept of IT, HNGU.
93
SQL Server Express uses the same reliable and high-performance database engine as the other versions of SQL Server 2005. It also uses the same data access APIs such as ADO.NET, SQL Native Client, and T-SQL. In fact, it is differentiated from the rest of the SQL Server 2005 editions only by the following:

Lack of enterprise features support Limited to one CPU One GB memory limit for the buffer pool Databases have a 4 GB maximum size
Features like Auto-Close and the ability to copy databases as files are enabled by default in SQL Server Express, while the high availability and business intelligence features are absent. It is very easy to "scale up" if that becomes necessary, as Express applications will work seamlessly with SQL Server 2005 Workgroup, Standard, or Enterprise editions. The Web download enables a free, fast, and convenient deployment. Key Features in SQL Server 2005 Express Edition SQL Server Express uses the same database engine as the rest of SQL Server 2005, and all the programmatic features are the same. The SQL engine supports 1 CPU, 1 GB RAM, and a 4 GB database size. This mechanism permits easy differentiation from other SQL Server 2005 editions by having well defined cut-off points. SQL Server Express can install and run on multiprocessor machines, but only a single CPU is used at any time. Multiple SQL Server 2005 Express installations can coexist on the same machine along with other installations of SQL Server 2000, SQL Server 2005, or Microsoft Desktop Engine (MSDE).
Dept of IT, HNGU.
94
Human Resources Management System In general, it is best that SQL Server 2000 instances be upgraded to Service Pack 4 (SP4). The maximum limit to the number of SQL Server Express instances is 16 on the same machine. These instances must be uniquely named for the purpose of identifying them. SQL Server Express is designed to be easy to use, and the graphical user interface (GUI) tools make it easy even for database novices to use the basic database functionalities in SQL Server Express. SQL Command is an OLE DB version of the existing SQL tool. It not only attempts to maintain functional compatibility with Sql, but also includes support for new SQL Server 2005 data types. All command line options output information to standard output, except error messages that may appear when an operation failed. SQL Browser is a new service in SQL Server 2005 that is used to identify the ports that named instances listen on. Since shared memory does not use it, this service is turned off in SQL Server Express by default. This means that the user will have to start this service so that network access can work. SQL Server 2005 Express supports the same native and managed providers as the rest of SQL Server 2005. This has the huge advantage that an application written for SQL Server Express will work seamlessly with other SQL Server editions. SQL Server 2005 Express supports ADO.NET for managed access. We recommend using the SqlClient data provider for developing new applications, since most of the application XCopy features is available only with SqlClient. The ADO.NET 2.0 data providers (available in Visual Studio 2005) support the new SQL Server data types like varchar (MAX) and XML, as well user-defined types. For SQL Server Express, goals are to provide secure defaults for the different components. For instance, the networking protocols such as TCP/IP and Named Pipes are turned off. SQL Browser service is not started unless the user explicitly asks for this in the setup command line. The SA or System Admin account is disabled by default if Windows Authentication is used.
Dept of IT, HNGU.
95
Human Resources Management System Normal users on the machine have almost no privileges on the SQL Server Express instance. A Local administrator on the server must explicitly grant relevant permissions for normal users so that they can use SQL functionality. User Instances are a new feature in SQL Server Express that provides the ability to treat databases like files. The local database can now be moved, copied, or e-mailed along with the application.
SQL Server Express setup is a simplified version of the SQL Server 2005 process. It is robust, reliable, and supports both GUI and the silent install modes. Only Windows Installer-based (.msi) technology is supported.
SQL Server Express Feature Components tree Feature Components GUI Feature Components Command Line Parameters: Provide a comma-delimited list with no spaces of the features to install after ADDLOCAL. SQL Server Database Services Data Files Replication Client Components SQL Command Line Tools Connectivity Components Software Development Kit SQL_Engine SQLEngine_Data_Files SQL_Replication Client_Components Server_tools Connectivity SDK
Dept of IT, HNGU.
96
LIMITATIONS & FUTURE ENHANCEMENT

9.1 LIMITATIONS
It requires .Net framework and IIS to run the .aspx files. All the pages and database are stored at server so if server goes down then system cant respond. 9.2 FUTURE ENHANCEMENT
There is always scope for enhancements in any system, are so in the ever- changing world of computers. The HRMS software can also be modified according to the future requirements and the advancement of the technology to increase the efficiency and adaptability of the system.
Dept of IT, HNGU.
97
CONCLUSION & DISCUSSION

10.1 SUMMARY OF PROJECT WORK
The usefulness of any system depends upon some of the basic things which are:
Dept of IT, HNGU.
98
Human Resources Management System Portability Reliability Maintainability Satisfaction Of User Requirements User Friendliness
Making a system 100% reliable is nearly an impossible thing. The system has been thoroughly tested by the developers and a team of experts and has tried to achieve reliability to its maximum extent. Thus it is safe to say that the system is reliable to the maximum possible extent.
The system is completely portable. It uses MS-SQL 2005 as the database and ASP.NET as the front end. The coding is also fully portable with minor changes on the implementation side.
The complete source is available with Panamax Infotech Limited., Ahemdabad. Each phase of the project is documented thoroughly. Both external documentation in the form of Requirements Study Documents and internal documentations in the form of comments in the program modules, specifications etc are available. So, in the future there should not be any problem to the maintenance of the system.
The HRMS has been designed by studying the existing process and requirements. So, it is perfect for the present scenario.
10.2 BIBILOGRAPHY BOOKS Beginning ASP.NET using VB.NET Chris Ullman. WEBSITES
Coding:www.codeguru.com www.asp.net/ajax www.codeproject.com www.rentacoder.com References:www.humanresources.co.in www.hr.com
Dept of IT, HNGU.
100

HRMiS Report2

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HRMiS Report2

Uploaded by

Copyright:

Available Formats

Human Resources Management System

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

1.4 TECHNOLOGY & LITERATURE REVIEW

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System where it belongs, and so on.

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

Desig Cod Increment-4

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

Dept of IT, HNGU.

Panamax InfoTech Limited

Dept of IT, HNGU.

Panamax InfoTech Limited

Dept of IT, HNGU.

Panamax InfoTech Limited

DB Design Coding Testing Documen-tation

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

2.2 RISK MANAGEMENT

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

SYSTEM REQUIREMENT STUDY (SRS)

3.2 HARDWARE & SOFTWARE REQUIREMENT

Human Resources Management System Web Design Tool: HTML

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

4.2 PROBLEM AND WEAKNESSES OF CURRENT SYSTEM

4.3 REQUIREMENTS OF NEW SYSTEM

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

4.3.5 SYSTEM SUPPORT REQUIREMENT

4.3.6 NON-FUNCTIONAL REQUIREMENTS

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

FOUR TESTS FOR FEASIBILITY

Dept of IT, HNGU.

Panamax InfoTech Limited

Human Resources Management System

Dept of IT, HNGU.

Panamax InfoTech Limited