Académique Documents
Professionnel Documents
Culture Documents
INTRODUCTION
A human resource category (for example, consultant, programmer, etc.) is a way of classifying skills that is useful in matching resource requirements to particular people when developing the human resource plan for a project. The Human resource plan contains for each human resource category, information such as: The number of staff required. Costing information and assumptions. When the staff are needed and for how long. Any special skills required over and above those that people in the category would normally be expected to have, as well as the required level of proficiency and the relative importance of these skills. Training requirements needed specifically for the project, for example in a new technology. Office and materiel requirements Plans for team-building activities. (Motivation management) The following column shows a sample portion of the Human resource plan for a project. Human Resource Category Number of staff Cost assumptions When needed Till what date the staff is needed Special skills, if any Special needs, if any Training needs, if any Office and material equipment
The Human Resource Plan supports staff planning, staff acquisition, allocating resources to staff, and supervising project specific training activities. A summary Human resource plan is created for the entire project and managed by the project manager. The formality with which the Human resource plan is created and documented is a reflection of the size and complexity of the project. Typically, small projects do not require a formal plan. On the other hand, large, multiyear, multilevel projects with many participants may require multiple formal plans. The HRM plan is based on the project schedule. 1.1 Objection of the project: In Order to be able to define our system architecture, we must first dearly state what our objective that will deriver system behavior at the same one of our objective is to create an experience, which is not only unique to the (user) client, but also makes him feel that he has loyal attachment to the system and approaches us whenever he/she needs. To achieve better results and success by implement computerized process instead of manual process. 1.2 Modules and their Description This project contains five main modules: 1. Home Module 2. Admin Module 3. Employee Module 4. Careers Module 5. E-test Module
1. Home Module:
It contains the details of the company.
2. Admin Module:
Admin module consists of following options. They are Employee Registration: This module is used to register the details of the new employee .Employee user creation is created to the particular employee.
Recruitment: This module is used to post the number of vacancies of the company. Question Entry: This module is used to post the questions and also the correct answer based on the domain which is used in the write exam module. Attendance Entry: Attendance entry of the particular employee is maintained here. Results: It is used to view the results of the candidates who attended the exams. Salary Structure: It is used to give the standard pay of the employee based on the designation. Salary Detail: It is used to view all the salary details of the employees and also used to give the other allowances and deductions. Send and Receive Message: It is used to send and receive message from the employees. View: It is used to view the Company profile, employee profile, salary detail, attendance detail.
3. Employee Module:
The Employee creation consists of following options. They are Company profile The company profile consists of company details. Employee profile The Employee profile consists of Employee details, employee id, and employee name. Attendance detail The Attendance details consist of employee daily attendance report. Salary detail: The salary module consists of salary detail of employee.
Send and Receive Message: It is used to send and receive message from the employees.
4. Career Module:
Career module consists of following options. They are Apply Job: The apply job is used to apply their resumes to the company. Search Job: It will help the people to search a job and is used to apply their resumes to the company.
5. E-Test Module:
E-Test consists of following options. They are Candidate Registration: This is used to register the details of the candidates such as name, address, qualification etc. Write Exam: Registered candidates write their exams based on the domain specified in the candidate registration. Result: It is used to give the marks of the candidates.
CHAPTER 2
SOFTWARE PROJECT PLAN
This chapter discuss about that time schedule for the project and it contain the various phases of the project.
TASK
Requirement Specification Requirement document specification Design analysis Design Documentation Design Review Coding Total
DURATION
10 Days 10 Days 20 Days 15 Days 20 Days 15 Days 90 Days
CHAPTER 3
CUSTOMER REQUIREMENTS DETERMINATION 3.1 Existing System
The existing system is manual system. Here student will attend exams to their company. It requires lot of time. The proposed system will handle this problem. Online examination is not handled here.
CHAPTER 4
SOFTWARE REQUIREMENTS SPECIFICATION
Software Requirements Specification (SRS) is the starting point of the software development activity. Little importance was given to this phases in the early days of software development. The emphasis was first on coding and then shifted to design. As systems grew more complex, it become evident that the goal of the entire system cannot be easily comprehended. Hence need for the requirements analysis phase arose. Now, for large software systems, requirements analysis is perhaps the most difficult activity and also the most error prone. Some of the difficulty is due to the scope of this phase. The software project is imitated by the client needs. In the beginning these needs are in the minds of various people in the client organization. The requirement analyst has to identify the requirements by tacking to these people and understanding there needs. In situations where the software is to automated a currently manuals process, most of the needs can be understood by observing the current practice. The SRS is a means of translating the ideas in the minds of the clients (the output) into formal document (the output of the requirements phase). Thus the output of the phase is a set of formally specified requirements, which hopefully are complete and consistent, while the input has none of these properties.
Login Communication
Company Profile Emp Detail Emp User Creation Attendance entry Salary Recruitment View resume Registration Result
Emp Registratio n
Employee
Test
HR
Question Entry
HRMS
E-Test
view
Communication
Login
Career
Apply Job
Search Job
PROCESSOR RAM MONITOR HARD DISK FLOPPY DRIVE CD DRIVE KEYBOARD MOUSE
: : : : : : : :
PENTIUM III 866 MHz 128 MD SD RAM 15 COLOR 20 GB 1.44 MB LG 52X STANDARD 102 KEYS 3 BUTTONS
To create project, add base masters and masters to the project, assign behaviors to the master, create and assign behavior sets, and then apply, test and validate those behaviors. It also shows how to create and build a stencil to hold the shapes.
CHAPTER 5
11
SYSTEM ANALYSIS
In this section discussed about data flow diagram, Entity relationship diagram. these things are represented as diagrams with proper notation. 5.1 DATA FLOW DIAGRAM The data flow diagram is one of the most improvement tools used by the system analyst DeMacro (1978) Nad Gand Sarson (1979) popularized the use if the data flow diagram as modeling tools through their structured system analysis methodologies. A data flow diagram should be the first tool used by system analyst to model system components. These components are the system processes; the data used by this processes and external entities that interact with the system and the information flows in the system. There are four kinds of system components 5.1.1. Process Process show what system does. Each process has one or more data inputs and produce one or more data output, Circles in a data flow diagram represent process. Each process has unique name and number. This name and number appear inside the circle that represents the processes in a data flow diagram. This process is represented as circle
12
File or data store is depositary of data. They contain data that is retained in the system. Processes can enter the data into a data store or retrieve data from the data store. Each data store is represented by thin line in the data flow diagram and each data store has a unique name. The data store is represented in form of a line
5.1.3 External Entities External entities are outside the system but they either supply input data into the system or use the system output, they are entities which the designer has no control. Square or rectangle may represent external entities that supply data into a system or some times called sources. External entities that use the system data are sometimes called sinks.
5.1.4 Data Flows Dataflow model the passage of data in the system and are represented lines joining system components. An arrow indicates the direction of the flow and the line labeled by the name of the data flow.
Admin Module
13
Admin Employee
Candidate Details
Recruitment
Questions
Resumes
Results
Attendance
Salary Details
Salary structure
Employee Module
14
Employee
Employee
Company profile
Employee Profile
Employee
Attendance Details
Attendance
Salary Details
Salary details
Career
Search Job
Apply Job
Career Module
15 Job
E-Test Module
E-Test
Candidate Registratio n
Result
Exam
Test Records
5.2 ER DIAGRAM
16
Login Communication
Company Profile Emp Detail Emp User Creation Attendance entry Salary Recruitment View resume Registration Result
Emp Registratio n
Employee
Test
HR
Question Entry
HRMS
E-Test
view
Communication
Login
Career
Apply Job
Search Job
17
Salary Structure
Employee
Salary Details
Admin Login
Client
Server
Admin
Valid user
Login
Invalid
Invalid User
Employee
Client Server Login Employee
Valid User
Invalid User
Job:
19
Client
Server
Job
Login
E-Test
Client Server E-Test
Login
20
Students DB
Learning Process
Training
Authorization Signatory
Coding
Validation
Testin g
Docume n
Reports
Certificate
Complete Certificate 21
CHAPTER 6
SYSTEM DESIGN
Design is multi-step process that focuses on data structure software architecture, procedural details, (algorithms etc.) and interface between modules. The design process also translates the requirements into the presentation of software that can be accessed for quality before coding begins. Computer software design changes continuously as new methods; better analysis and broader understanding evolved. Software Design is at relatively early stage in its revolution. Therefore, Software Design methodology lacks the depth, flexibility and quantitative nature that are normally associated with more classical engineering disciplines. However techniques for software designs do exist, criteria for design qualities are available and design notation can be applied.
22
6.3 INTERFACE DESIGN The ODBC (Open Database Connectivity) interface is a pure .NET to execute SQL statement. The ODBC provides a set classes and interfaces that can be used by developers to write database applications. Basic ODBC interactions in its simplest form, can be broken down into four steps: 1. Open a connection to the database. 2. Execute a SQL statement 3. Process the result 4. Close the connection to the database
23
Attendance Detail
Candidate Detail
Communication
24
Employee Details
Employee Login
Job Posted
25
Questions
Requirements
Resume
26
Salary details
Salary Details
27
Each of these models can take full advantage of all ASP.NET features, as well as the power of the .NET Framework and .NET Framework common language runtime. Accessing databases from ASP.NET applications is an often-used technique for displaying data to Web site visitors. ASP.NET makes it easier than ever to access databases for this purpose. It also allows us to manage the database from your code . ASP.NET provides a simple model that enables Web developers to write logic that runs at the application level. Developers can write this code in the global.aspx text file or in a compiled class deployed as an assembly. This logic can include application-level events, but developers can easily extend this model to suit the needs of their Web application. ASP.NET provides easy-to-use application and session-state facilities that are familiar to ASP developers and are readily compatible with all other .NET Framework APIs.ASP.NET offers the IHttpHandler and IHttpModule interfaces. Implementing the IHttpHandler interface gives you a means of interacting with the low-level request and response services of the IIS Web server and provides functionality much like ISAPI extensions, but with a simpler programming model. Implementing the IHttpModule interface allows you to include custom events that participate in every request made to your application. ASP.NET takes advantage of performance enhancements found in the .NET Framework and common language runtime. Additionally, it has been designed to offer significant performance improvements over ASP and other Web development platforms. All ASP.NET code is compiled, rather than interpreted, which allows early binding, strong typing, and just-in-time (JIT) compilation to native code, to name only a few of its benefits. ASP.NET is also easily factorable, meaning that developers can remove modules (a session module, for instance) that are not relevant to the application they are developing. ASP.NET provides extensive caching services (both built-in services and caching APIs). ASP.NET also ships with performance counters that developers and system administrators can monitor to test new applications and gather metrics on existing applications. Writing custom debug statements to your Web page can help immensely in troubleshooting your application's code. However, it can cause embarrassment if it is not removed. The problem is that removing the debug statements from your pages when your application is ready to be ported to a production server can require significant effort. ASP.NET offers the Trace Context class, which allows us to write custom debug statements to our pages as we develop them. They appear only when you have enabled tracing for a page or entire application. Enabling tracing also appends details about a request to the page, or, if you so specify, to a custom trace viewer that is stored in the root directory of your 29
application. The .NET Framework and ASP.NET provide default authorization and authentication schemes for Web applications. we can easily remove, add to, or replace these schemes, depending upon the needs of our application . ASP.NET configuration settings are stored in XML-based files, which are human readable and writable. Each of our applications can have a distinct configuration file and we can extend the configuration scheme to suit our requirements. DATA ACCESS WITH ADO.NET As you develop applications using ADO.NET, you will have different requirements for working with data. You might never need to directly edit an XML file containing data - but it is very useful to understand the data architecture in ADO.NET. ADO.NET offers several advantages over previous versions of ADO Interoperability Maintainability Programmability Performance Scalability INTEROPERABILITY ADO.NET applications can take advantage of the flexibility and broad acceptance of XML. Because XML is the format for transmitting datasets across the network, any component that can read the XML format can process data. The receiving component need not be an ADO.NET component. The transmitting component can simply transmit the dataset to its destination without regard to how the receiving component is implemented. The destination component might be a Visual Studio application or any other application implemented with any tool whatsoever. The only requirement is that the receiving component be able to read XML. SO, XML was designed with exactly this kind of interoperability in mind.
MAINTAINABILITY In the life of a deployed system, modest changes are possible, but substantial, Architectural changes are rarely attempted because they are so difficult. As the performance load on a deployed application server grows, system resources can become scarce and response 30
time or throughput can suffer. Faced with this problem, software architects can choose to divide the server's business-logic processing and user-interface processing onto separate tiers on separate machines. In effect, the application server tier is replaced with two tiers, alleviating the shortage of system resources. If the original application is implemented in ADO.NET using datasets, this transformation is made easier. ADO.NET data components in Visual Studio encapsulate data access functionality in various ways that help you program more quickly and with fewer mistakes. PERFORMANCE ADO.NET datasets offer performance advantages over ADO disconnected record sets. In ADO.NET data-type conversion is not necessary. SCALABILITY ADO.NET accommodates scalability by encouraging programmers to conserve limited resources. Any ADO.NET application employs disconnected access to data; it does not retain database locks or active database connections for long durations. VISUAL STUDIO .NET Visual Studio .NET is a complete set of development tools for building ASP Web applications, XML Web services, desktop applications, and mobile applications In addition to building high-performing desktop applications, you can use Visual Studio's powerful component-based development tools and other technologies to simplify team-based design, development, and deployment of Enterprise solutions. Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same integrated development environment (IDE), which allows them to share tools and facilitates in the creation of mixed-language solutions. In addition, these languages leverage the functionality of the .NET Framework and simplify the development of ASP Web applications and XML Web services. Visual Studio supports the .NET Framework, which provides a common language runtime and unified programming classes; ASP.NET uses these components to create ASP Web applications and XML Web services. Also it includes MSDN Library, which contains all the documentation for these development tools.
31
THE .NET FRAMEWORK The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. OBJECTIVES OF. NET FRAMEWORK 1. To provide a consistent object-oriented programming environment whether object codes is stored and executed locally on Internet-distributed, or executed remotely. 2. To provide a code-execution environment to minimizes software deployment and guarantees safe execution of code. 3. Eliminates the performance problems There are different types of application, such as Windows-based applications and Web-based applications. To make communication on distributed environment to ensure that code be accessed by the .NET Framework can integrate with any other code. COMPONENTS OF .NET FRAMEWORK 1. THE COMMON LANGUAGE RUNTIME (CLR) The common language runtime is the foundation of the .NET Framework. It manages code at execution time, providing important services such as memory management, thread management, and remoting and also ensures more security and robustness. The concept of code management is a fundamental principle of the runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code THE .NET FRAME WORK CLASS LIBRARY It is a comprehensive, object-oriented collection of reusable types used to develop applications ranging from traditional command-line or graphical user interface (GUI) applications to applications based on the latest innovations provided by ASP.NET, such as Web Forms and XML Web services. The .NET Framework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the execution of managed code, thereby creating a software environment that can exploit both managed and unmanaged features. The .NET Framework not only provides several runtime hosts, but also supports the development of third-party runtime hosts. 32
Internet Explorer is an example of an unmanaged application that hosts the runtime (in the form of a MIME type extension). Using Internet Explorer to host the runtime to enables embeds managed components or Windows Forms controls in HTML documents. FEATURES OF THE COMMON LANGUAGE RUNTIME The common language runtime manages memory; thread execution, code execution, code safety verification, compilation, and other system services these are all run on CLR. Security. Robustness. Productivity. Performance. SECURITY The runtime enforces code access security. The security features of the runtime thus enable legitimate Internet-deployed software to be exceptionally feature rich. With regards to security, managed components are awarded varying degrees of trust, depending on a number of factors that include their origin to perform file-access operations, registry-access operations, or other sensitive functions. ROBUSTNESS The runtime also enforces code robustness by implementing a strict type- and codeverification infrastructure called the common type system(CTS). The CTS ensures that all managed code is self-describing. The managed environment of the runtime eliminates many common software issues
PRODUCTIVITY The runtime also accelerates developer productivity. For example, programmers can write applications in their development language of choice, yet take full advantage of the runtime, the class library, and components written in other languages by other developers.
33
PERFORMANCE The runtime is designed to enhance performance. Although the common language runtime provides many standard runtime services, managed code is never interpreted. A feature called just-in-time (JIT) compiling enables all managed code to run in the native machine language of the system on which it is executing. Finally, the runtime can be hosted by highperformance, server-side applications, such as Microsoft SQL Server and Internet Information Services (IIS).
TABLE: A database is a collection of data about a specific topic. VIEWS OF TABLE: We can work with a table in two types, 34
1. Design View 2. Datasheet View Design View To build or modify the structure of a table we work in the table design view. We can specify what kind of data will be hold. Datasheet View To add, edit or analyses the data itself we work in tables datasheet view mode. QUERY A query is a question that has to be asked the data. Access gathers data that answers the question from one or more table. The data that make up the answer is either dataset (if you edit it) or a snapshot (it cannot be edited).Each time we run query, we get latest information in the dataset. Access either displays the dataset or snapshot for us to view or perform an action on it, such as deleting or updating. FORMS A form is used to view and edit information in the database record by record .A form displays only the information we want to see in the way we want to see it. Forms use the familiar controls such as textboxes and checkboxes. This makes viewing and entering data easy. Views of Form We can work with forms in several primarily there are two views, They are, 1. Design View 2. Form View Design View To build or modify the structure of a form, we work in forms design view. We can add control to the form that are bound to fields in a table or query, includes textboxes, option buttons, graphs and pictures. Form View 35
The form view which display the whole design of the form. REPORT A report is used to vies and print information from the database. The report can ground records into many levels and compute totals and average by checking values from many records at once. Also the report is attractive and distinctive because we have control over the size and appearance of it. MACRO A macro is a set of actions. Each action in macros does something. Such as opening a form or printing a report .We write macros to automate the common tasks the work easy and save the time. MODULE Modules are units of code written in access basic language. We can write and use module to automate and customize the database in very sophisticated ways.It is a personal computer based RDBMS. This provides most of the features available in the high-end RDBMS products like Oracle, Sybase, and Ingress etc.
Step5: The employee attendance details, salary details, salary calculation can be viewed. Step 6: The employee can send the messages and received the messages to another employee. Step 7: After the user how to apply the job and the number of job vacancies to be viewed. Step 8: The user can be apply the job for online and then the user will be participated in the e-test. Step 9: Finally to view the e-test results and the new employee can register the particular details.
CHAPTER 7
CODINGS
37
Attendance detail
using System; using System.Collections; using System.ComponentModel; using System.Data; using System.Data.SqlClient; using System.Drawing; using System.Web; using System.Web.SessionState; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.HtmlControls; namespace hrmsprojecting.Employee { /// <summary> /// Summary description for WebForm2. /// </summary> public class WebForm2 : System.Web.UI.Page { protected System.Web.UI.WebControls.DataList DataList1; protected System.Web.UI.WebControls.HyperLink HyperLink1; SqlConnection con = new SqlConnection("server=.;database=HRMSPrj;uid=sa;"); private void Page_Load(object sender, System.EventArgs e) { // Put user code to initialize the page here con.Open(); DataSet ds = new DataSet(); string eid = Convert.ToString(Session["empid"]); SqlDataAdapter adp = new SqlDataAdapter("select * from Attendence where EmployeeId='"+ eid +"'",con); adp.Fill(ds); DataList1.DataSource = ds; DataList1.DataBind(); con.Close();
38
} #region Web Form Designer generated code override protected void OnInit(EventArgs e) { // // CODEGEN: This call is required by the ASP.NET Web Form Designer. // InitializeComponent(); base.OnInit(e); } /// <summary> /// Required method for Designer support - do not modify /// the contents of this method with the code editor. /// </summary> private void InitializeComponent() { this.DataList1.SelectedIndexChanged += new System.EventHandler(this.DataList1_SelectedIndexChanged); this.Load += new System.EventHandler(this.Page_Load); } #endregion private void DataList1_SelectedIndexChanged(object sender, System.EventArgs e) { } }
Write Test
using System; using System.Collections; using System.ComponentModel; using System.Data;
39
using System.Drawing; using System.Web; using System.Web.SessionState; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.HtmlControls; using System.Data.SqlClient; namespace WebApplication20 { /// <summary> /// Summary description for WebForm4. /// </summary> public class WebForm4 : System.Web.UI.Page { protected System.Web.UI.HtmlControls.HtmlAnchor hrefFirst; protected System.Web.UI.HtmlControls.HtmlAnchor hrefPrevious; protected System.Web.UI.HtmlControls.HtmlAnchor hrefNext; protected System.Web.UI.HtmlControls.HtmlAnchor hrefLast; protected System.Web.UI.WebControls.Label mess; protected System.Web.UI.WebControls.Label intPageSize; protected System.Web.UI.WebControls.Label intRecordCount; protected System.Web.UI.WebControls.Label intCurrIndex; protected System.Web.UI.WebControls.Label lblStatus; protected System.Web.UI.WebControls.Button Button1; protected System.Web.UI.WebControls.DataList DataList1;
#region Web Form Designer generated code override protected void OnInit(EventArgs e) { InitializeComponent(); base.OnInit(e); } /// <summary> /// Required method for Designer support - do not modify /// the contents of this method with the code editor. /// </summary>
40
private void InitializeComponent() { this.DataList1.SelectedIndexChanged += new System.EventHandler(this.DataList1_SelectedIndexChanged); this.Button1.Click += new System.EventHandler(this.Button1_Click); this.Load += new System.EventHandler(this.Page_Load); } #endregion private void Page_Load(object sender, System.EventArgs e) { if (!Page.IsPostBack) { intPageSize.Text = "10"; intCurrIndex.Text = "0"; DataBinds(); } }
public void {
DataBinds()
string domain=Convert.ToString(Session["Domain"]); SqlConnection objConn = new SqlConnection("database=HRMSPrj;server=.;uid=sa;"); SqlDataAdapter objDA = new SqlDataAdapter("select * from question where domain='"+ domain +"'", objConn); DataSet objDS = new DataSet(); if (!Page.IsPostBack ) { objDA.Fill(objDS); intRecordCount.Text =Convert.ToString(objDS.Tables[0].Rows.Count); objDS = null; objDS = new DataSet();
41
} objDA.Fill(objDS, Convert.ToInt16(intCurrIndex.Text), Convert.ToInt16(intPageSize.Text), "Sales"); DataList1.DataSource = objDS.Tables[0].DefaultView; DataList1.DataBind(); objConn.Close(); PrintStatus(); } public void ShowFirst(object s, EventArgs e) { intCurrIndex.Text = "0"; DataBinds(); }
public void ShowPrevious(object s, EventArgs e) { int a=Convert.ToInt16(intCurrIndex.Text); int b=Convert.ToInt16(intPageSize.Text); intCurrIndex.Text = Convert.ToString(a-b); if ( Convert.ToInt16(intCurrIndex.Text) < 0) { intCurrIndex.Text = "0"; } DataBinds(); } public void ShowNext(object s, EventArgs e) { if ( Convert.ToInt16( intCurrIndex.Text) + 1 < Convert.ToInt16(intRecordCount.Text)) { intCurrIndex.Text = Convert.ToString( Convert.ToInt16(intCurrIndex.Text) + Convert.ToInt16(intPageSize.Text)); }
42
DataBinds(); } public void ShowLast(object s, EventArgs e) { int tmpInt; tmpInt = Convert.ToInt16(intRecordCount.Text) % Convert.ToInt16(intPageSize.Text); if (tmpInt > 0) { intCurrIndex.Text = Convert.ToString((Convert.ToInt16(intRecordCount.Text) - tmpInt)); } else { intCurrIndex.Text = (Convert.ToInt16( intRecordCount.Text) Convert.ToInt16( intPageSize.Text)); } DataBinds(); } private void PrintStatus() { lblStatus.Text = "Total Records:<b>" + intRecordCount.Text; lblStatus.Text += "</b> - Showing Page:<b> "; lblStatus.Text += 1)); lblStatus.Text += "</b> of <b>"; if (( Convert.ToInt16(intRecordCount.Text) % Convert.ToInt16( intPageSize.Text)) > 0) { lblStatus.Text += Convert.ToString( Convert.ToInt16(intRecordCount.Text) /Convert.ToInt16( intPageSize.Text + 1)); } else Convert.ToString (Convert.ToInt16(intCurrIndex.Text) / Convert.ToInt16(intPageSize.Text + Convert.ToString
43
{ lblStatus.Text += Convert.ToString (Convert.ToInt16(intRecordCount.Text) / Convert.ToInt16(intPageSize.Text)); } lblStatus.Text += "</b>"; } protected void Button1_Click(object sender, System.EventArgs e) { string r1; string r2; string r3; string r4; string r5; int marks=0;
DataList1.Items)
44
if (r2==r5) { marks=marks+1; } }
if( ((RadioButton)anItem.FindControl("RadioButton4")).Checked) { r4= ((RadioButton)anItem.FindControl("RadioButton4")).Text; r5= ((TextBox)anItem.FindControl("TextBox1")).Text; if (r4==r5) { marks=marks+1; } } } SqlConnection con=new SqlConnection("server=.;database=HRMSPrj;uid=sa") string m = Convert.ToString(Session["cno"]); con.Open(); Session["ScoredMarks"]=Convert.ToInt32(marks); SqlCommand cmd = new SqlCommand();
45
cmd.CommandText = "update candidatesdetails set marks="+ marks +" where cno="+ m +""; cmd.Connection=con; cmd.ExecuteNonQuery(); con.Close(); Response.Redirect("ResultCand.aspx");
46
protected System.Web.UI.WebControls.TextBox txt_HRA; protected System.Web.UI.WebControls.TextBox txt_MedicalAlv; protected System.Web.UI.WebControls.TextBox txt_ProffTax; protected System.Web.UI.WebControls.TextBox txt_PF; protected System.Web.UI.WebControls.Button Button2; protected System.Web.UI.WebControls.DropDownList drDesignation; protected System.Web.UI.WebControls.Label lblvalidation; protected System.Web.UI.WebControls.TextBox txt_Convayence; protected System.Web.UI.WebControls.Label lbl_write; protected System.Web.UI.WebControls.HyperLink HyperLink1; SqlConnection con = new SqlConnection("server=.;database=HRMSPrj;uid=sa;"); private void Page_Load(object sender, System.EventArgs e) { // Put user code to initialize the page here } #region Web Form Designer generated code override protected void OnInit(EventArgs e) { InitializeComponent(); base.OnInit(e); }
private void InitializeComponent() { this.Button1.Click += new System.EventHandler(this.Button1_Click); this.Button2.Click += new System.EventHandler(this.Button2_Click); this.Load += new System.EventHandler(this.Page_Load); } #endregion private void Button1_Click(object sender, System.EventArgs e) {
47
if(drDesignation.SelectedItem.Text=="Select") { lblvalidation.Text="Select Designation"; lblvalidation.Visible=true; } else { con.Open(); SqlCommand cmd = new SqlCommand(); cmd.CommandText="insert into SalaryStructure values('"+ drDesignation.SelectedItem.Text +"',"+ txt_basicpay.Text +","+ txt_HRA.Text +","+ txt_MedicalAlv.Text +","+ txt_Convayence.Text +","+ txt_ProffTax.Text +","+ txt_PF.Text +")"; cmd.Connection=con; cmd.ExecuteNonQuery(); lbl_write.Text="Salary Structure Made Successfully..."; lbl_write.Visible=true; con.Close(); txt_basicpay.Text=""; txt_HRA.Text=""; txt_MedicalAlv.Text=""; txt_Convayence.Text=""; txt_ProffTax.Text=""; txt_PF.Text=""; } } }
CHAPTER 8
48
SYSTEM TESTING
System testing involves user training system testing and successful running of the developed proposed system. The user tests the developed system and changes are made according to their needs. The testing phase involves the testing of developed system using various kinds of data. An elaborate testing of data is prepared and the system is tested using the test data. While testing, errors are noted and the corrections are made. The corrections are also noted for the future use. The users are trained to operate the developed system. TESTING System testing is the stage of implementation that is aimed at ensuring that the system works accurately and efficiently before live operation commences. Testing is vital to the success of the system. System testing makes logical assumption that if all the parts of the system are correct, then the goal will be successfully achieved. A series of testing are done for the proposed system before the system is ready for the user acceptance testing. The following are the types of Testing Unit Testing Integration Testing 1. Validation Testing 2. Verification testing 3. User acceptance testing 9.1 Unit Testing Unit testing focuses verification efforts on the smallest unit of the software design, the module. This is also known as module testing. The modules are tested separately. This testing was carried out during programming stage itself. In this testing each module is found to be working satisfactorily as regards to the expected output from the module.
49
Data can be lost across an interface: one module can have adverse efforts on another. Integration testing is the systematic testing for construction of program structure, while at the same time conducting tests to uncover errors associated within the interface. Here correction is difficult because the isolation of cause is complicated by the cast expense of the entire program. Thus in the integration testing step, all the errors uncovered are corrected for the next testing steps. 9.3 Validation Testing At the conclusion of integration testing, software is completely assembled as a package, interfacing errors have been uncovered and corrected and a final series of software tests begins validation test has been conducted one of the two possible conditions exists. One is the function or performance characteristics confirm to specification and are accepted and the other is deviation from specification is uncovered and a deficiency list is created.
CHAPTER 9
50
PROBLEMS FACED
When there is a clear goal in sight but no clear set of directions or means to attain that goal, then it is called a problem. problems can be broken down into four aspects; goal, givens, means of transforming conditions, and obstacles. Goal the goal is the desired end state which the problem solving is being directed toward. The hope is to reach that end state and be able to assess whether or not you achieved what you wanted. Givens- these are the objects , conditions ,and constraints that accompany a problem ,and can be either explicit or implicit. Means of transforming conditions- there should be a way of changing the initial stateof the problem.this is most usually a persons knowledge or skill level. For instance ,a computer programmer presented with a problem would utilize his or her knowledge of programming language to transform the state of the problem. Obstacles- the problem should present a challenge.if there are no challenges involved and the situation can be easily solved then it is not so a problem so much as a rountine task. Every problem has a problem faced, which is the whole range of possible states and operators.only some of these states and operators will bring the person closer to the goal state. The problem starts at the initial state and operators are applied to change the state, creating a series of intermediate states that should hopefully lead to the final goal state
51
CHAPTER 10
FUTURE PLANS
Every application has its own merits and demerits. The project has covered almost all the requirements. Further requirements and improvements can easily be done since the coding is mainly structured or modular in nature. Changing the existing modules or adding new modules can append improvements. Further enhancements can be made to the application, so that the web site functions very attractive and useful manner than the present one
CONCLUSION
52
It is concluded that the application works well and satisfy the company and students. The application is tested very well and errors are properly debugged. The site is simultaneously accessed from more than one system. Simultaneous login from more than one place is tested. The site works according to the restrictions provided in their respective browsers. Further enhancements can be made to the application, so that the web site functions very interactive and useful to existing application .The application satisfies both the company and students by eliminating more input. The speed of the transactions become more enough now.
APPENDIX
53
Fig 1.Home
54
55
56
57
58
59
60
61
62
63
64
65
66
67
Fig 15.View
68
69
70
71
72
73
Fig 21.Careers
74
75
76
77
78
REFERENCES
Book Reference
Professional ASP.NET MVC 1.0 (Wrox Programmer to Programmer) / Rob Conery, Scott Hanselman, Phil Haack, Scott Guthrie Publisher: Wrox ASP.NET 3.5 Unleashed / Stephen Walther Publisher: Sams Programming ASP.NET 3.5 / Jesse Liberty, Dan Maharry, Dan Hurwitz Publisher: O'Reilly Media, Inc.
79
BIBLIOGRAPHY
80