1. INTRODUCTION 1.1.

INTRODUCTION TO ONLINE JOB PORTAL

This project is aimed at developing an online search Portal for the Placement Details for job seekers. The system is an online application that can be accessed throughout the organization and outside as well with proper login provided. This system can be used as an Online Job Portal for job seekers. Job eekers logging should be able to upload their information in the form of a !". "isitors#!ompany representatives logging in may also access#search any information put up by Job aspirants. .

$%$

1.2.

ORGANIZATION PROFILE
&oresight oftware olutions is one of the upcoming oftware Developing

!ompany in 'ndia. &oresight mainly indulges in

oftware Development which

includes mainly ( major application heads. They are )indows applications* )eb applications* and +iometric applications. These include various well known and commonly used application software,s like .net* J-..* Java* P/P* Dreamweaver* 0dobe* !oral Designer* (D 1a2* and &lash which helps in making the development process more efficient. &oresight constitutes various departments. These departments handle the various functions of the centre. The various departments are3 Programming department* Designing department* 1arketing department* Projects department and Training department. &oresight also deals with handling !ustomized Projects. These projects consider the opinions from the customers and are designed according to their views. This includes - categories. They are3 )eb and )indows designed projects. &oresight software solutions established in the year -445 is one of the leading software development companies in !oimbatore in 'T industry. 't is an e2clusive offshore software development centre addressed to meet the '.T needs in 'ndia* the 1iddle .ast and the 0sia Pacific region.. The oftware Division specializes in ystem 6evel* 7etwork !ommunication and 'nternet programming applications especially web applications with e2tensive usage of multimedia tools for better user interactions and effectiveness of conveying concepts and ideas. 0s we look ahead to what the fast approaching future will bring to us and demand from us* we look to strengthen the foundations of the organization today. )e have attracted additional e2pert talent to support our core competencies* and focused our marketing strategy. oftware

$-$

1.3.

PROBLEM IN EXISTING SYSTEM The present system abides a 1anual system. 't8s &unctions such as Job

Posting* student registration* interview process* status and job details are maintained manually. The information provided by the present system re9uires a lot of manual interventions at the time of preparing the system. /ence there is a need for updating of the system. 1.4. !annot :pload and Download the latest updates. 7o use of )eb ervices and ;emoting. ;isk of mismanagement and of data when the project is under development. 6ess ecurity. 7o proper coordination between different 0pplications and :sers. &ewer :sers $ &riendly.

SOLUTION OF THESE PROBLEMS

The development of the new system contains the following activities* which try to automate the entire process keeping in view of the database integration approach. %. :ser friendliness is provided in the application with various controls. -. The system makes the overall project management much easier and fle2ible. (. ;eadily upload the latest updates* allows user to download the alerts by clicking the :;6. <. There is no risk of data mismanagement at any level while the project development is under process. =. 't provides high level of security with different level of authentication.

$($

2. SYSTEM ANALYSIS
2.1. INTRODUCTION
0fter analyzing the re9uirements of the task to be performed* the ne2t step is to analyze the problem and understand its conte2t. The first activity in the phase is studying the e2isting system and other is to understand the re9uirements and domain of the new system. +oth the activities are e9ually important* but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. :nderstanding the properties and re9uirements of a new system is more difficult and re9uires creative thinking and understanding of e2isting running system is also difficult* improper understanding of present system can lead diversion from solution.

2.2. ANALYSIS MODEL

The model that is basically being followed is the )0T.; &066 1OD.6* which states that the phases are organized in a linear order. &irst of all the feasibility study is done. Once that part is over the re9uirement analysis and project planning begins. 'f system e2ists one and modification and addition of new module is needed* analysis of present system can be used as basic model. The design starts after the re9uirement analysis is complete and the coding begins after the design is complete. Once the programming is completed* the testing is done. 'n this model the se9uence of activities performed in a software development project are3 $ ;e9uirement 0nalysis Project Planning ystem design Detail design !oding :nit testing ystem integration > testing

$<$

/ere the linear ordering of these activities is critical. .nd of the phase and the output of one phase is the input of other phase. The output of each phase is to be consistent with the overall re9uirement of the system. ome of the 9ualities of spiral model are also incorporated like after the people concerned with the project review completion of each of the phase the work done. )0T.; &066 1OD.6 was being chosen because all re9uirements were known beforehand and the objective of our software development is the computerization#automation of an already e2isting manual working system.

C anged Requirements Communicated Requirements

Requirements Engineering

Requirements Specification

Design

Design Specification

Programming

Executable Software Modules

Maintenance

Process

Integration

Integrated Software Product

Product Input

Product Output

Deliver!

Delivered Software Product

Fig 2.2:

!"#$ F!%% M&'#%

$=$

2.3. STUDY OF THE SYSTEM

GUI(S 'n the fle2ibility of the uses the interface has been developed a graphics concept in mind* associated through a browses interface. The ?:'8 at the top level have been categorized as %. 0dministrative user interface -. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is practically* part of the organizational activities and which needs proper authentication for the data collection. The interfaces help the administrations with all the transactional states like Data insertion* Data deletion and Date updation along with the e2tensive data search capabilities. The operational or generic user interface helps the users upon the system in transactions through the e2isting data and re9uired services. The operational user interface also helps the ordinary users in managing their own information helps the ordinary users in managing their own information in a customized manner as per the assisted fle2ibilities. NUMBER OF MODULES The system after careful analysis has been identified to be presented with the following modules3 T)# *&'+%#, i-.&%.#' !$#: 0dmin Job eeker Job Provider 7otification earch ;eport 0uthentication

$@$

A'*i'n this module 0dmin will add all the 9ualifications* skill* e2perience* city* state* country and update and delete information about the job provider or job seeker he can also search for the job seeker and he can send mail to offer the job to job seeker and he can also see the jobs add by the job provider. J&/ S##0#$ 'n this module Job eeker register himself and upload his resume and fill the profile give by admin and after login he will search for the job on various conditions and he can change his profiles and resume and he can apply for the jobs based on various conditions. /e can see the response of the company and he can call the company person for the interview. J&/ 1$&.i'#$ 'n this module Job Provider register himself and his company and after login he will add new job and he can search for the job seekers on various condition and he can offer the job to job seeker according to the job profile and he can also see the response from the job seekers and send the mail. N&"i2i3!"i&'n this module admin and job provider send the notification to the job seeker in the form of email. R#1&$",:4 This module contains all the information about the reports generated by the admin based on the particular job seeker* particular job provider* all job seeker and job provider* all jobs generated by the job providers. A+")#-"i3!"i&-:4 This module contains all the information about the authenticated user. :ser without his username and password can8t enter into the login if he is only the authenticated user then he can enter to his login.

$5$

2.4. HARD ARE SPECIFICATIONS

HARD ARE RE5UIREMENTS: SOFT P'" -.A ?/z Processor and 0bove ;01 =%-1+ and 0bove /DD -4 ?+ /ard Disk pace and 0bove ARE RE5UIREMENTS: )'7DO) O BCP # -444 # -44 erver # -44( erverD "isual tudio .7et -44= .nterprise .dition 'nternet 'nformation erver =.4 B'' D "isual tudio .7et &ramework B1inimal for DeploymentD E6 erver -444 .nterprise .dition

2.6. PROPOSED SYSTEM

To debug the e2isting system* remove procedures those cause data redundancy* make navigational se9uence proper. To provide information about audits on different level and also to reflect the current work status depending on organization#auditor or date. To build strong password mechanism.

NEED FOR COMPUTERIZATION

)e all know the importance of computerization. The world is moving ahead at lightening speed and every one is running short of time. One always wants to get the information and perform a task he#she#they desireBsD within a short period of time and too with amount of efficiency and accuracy. The application areas for the computerization have been selected on the basis of following factors3

$A$

1inimizing the manual records kept at different locations. There will be more data integrity. &acilitating desired information display* very 9uickly* by retrieving information from users. &acilitating various statistical information which helps in decision$makingF To reduce manual efforts in activities that involved repetitive work. :pdating and deletion of such a huge amount of data will become easier.

FUNCTIONAL FEATURES OF THE MODEL

0s far as the project is developed the functionality is simple* the objective of the proposal is to strengthen the functioning of 0udit tatus 1onitoring and make them effective and better. The entire scope has been classified into five streams knows as !oordinator 6evel* management 6evel* 0uditor 6evel* :ser 6evel and tate )eb !oordinator 6evel. The proposed software will cover the information needs with respect to each re9uest of the user group viz. accepting the re9uest* providing vulnerability document report and the current status of the audit.

OR7ING OF THE SYSTEM

The entire scope has been classified into five streams known as3 $ C&&$'i-!"&$ L#.#% B0ddressing the information management needs of coordinatorD M!-!g#*#-" L#.#% B0ddressing the information management needs of managementD A+'i"&$ L#.#% B0ddressing the information management needs of auditorsD U,#$ L#.#% B0ddressing the information management needs of the user groupD S"!"# #/ C&&$'i-!"&$ %#.#% B0ddressing the needs of coordinator of the stateD

$G$

2.8. INPUT AND OUTPUT

The main inputs* outputs and major functions of the system are as follows INPUTS: /ead operator enters his or her user id and password. Operators enter his or her user id and password. Technicians enter his or her user id and password. ub technicians enter his or her user id and password. :ser re9uests the reports. :ser re9uests the search. /ead operator can edits the personal details and so on.

OUTPUTS: /ead operator receives personal details. Operator receives the personal details. Technicians receive personal and technical details. :sers receive re9uested reports. Displays search result.

$ %4 $

2.9. PROCESS MODELS USED

ACCESS CONTROL FOR

ITH JUSTIFICATION
HICH RE5UIRE USER

DATA

AUTHENTICATION

The following commands specify access control identifiers and they are typically used to authorize and authenticate the user Bcommand codes are shown in parenthesesD USER NAME :USER; The user identification is that which is re9uired by the server for access to its file system. This command will normally be the first command transmitted by the user after the control connections are made Bsome servers may re9uire thisD. PASS ORD :PASS;

This command must be immediately preceded by the user name command* and* for some sites* completes the user,s identification for access control. out. ince password information is 9uite sensitive* it is desirable in general to HmaskH it or suppress type

$ %% $

3. FEASIBILITY REPORT
Preliminary investigation e2amine project feasibility* the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical* Operational and .conomical feasibility for adding new modules and debugging old running system. 0ll system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation3 Technical &easibility Operation &easibility .conomical &easibility

3.1. T#3)-i3!% F#!,i/i%i"< The technical issue usually raised during the feasibility stage of the investigation includes the following3 Does the necessary technology e2ist to do what is suggestedF Do the proposed e9uipments have the technical capacity to hold the data re9uired to use the new systemF )ill the proposed system provide ade9uate response to in9uiries* regardless of the number or location of usersF !an the system be upgraded if developedF 0re there technical guarantees of accuracy* reliability* ease of access and data securityF .arlier no system e2isted to cater to the needs of I ecure 'nfrastructure 'mplementation ystem8. The current system developed is technically feasible. 't is a web based user interface for audit workflow at 7'!$! D. Thus it provides an easy access to the users. The database8s purpose is to create* establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore* it provides the technical guarantee of accuracy* reliability and security. The software and hard re9uirements for the development of this project are not many and are already available in$house at 7'! or are available as free as $ %- $

open source. The work for the project is done with the current e9uipment and e2isting software technology. 7ecessary bandwidth e2ists for providing a fast feedback to the users irrespective of the number of users using the system.

3.2. O1#$!"i&-!% F#!,i/i%i"< Proposed projects are beneficial only if they can be turned out into information system. That will meet the organization8s operating re9uirements. Operational feasibility aspects of the project are to be taken as an important part of the project implementation. ome of the important issues raised are to test the operational feasibility of a project includes the following3 $ 's there sufficient support for the management from the usersF )ill the system be used and work properly if it is being developed and implementedF )ill there be any resistance from the user that will undermine the possible application benefitsF This system is targeted to be in accordance with the above$mentioned issues. +eforehand* the management issues and user re9uirements have been taken into consideration. o there is no 9uestion of resistance from the users that can undermine the possible application benefits. The well$planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status.

3.3. E3&-&*i3 F#!,i/i%i"< 0 system can be developed technically and that will be used if installed must still be a good investment for the organization. 'n the economical feasibility* the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. &inancial benefits must e9ual or e2ceed the costs. The system is economically feasible. 't does not re9uire any addition hardware or software. ince the interface for this system is developed using the e2isting resources and technologies available at 7'!* There is nominal e2penditure and economical feasibility for certain. $ %( $

4. SOFT

ARE RE5UIREMENT SPECIFICATION

The software* ite .2plorer is designed for management of web sites from a remote location. INTRODUCTION P+$1&,#: The main purpose for preparing this document is to give a general insight into the analysis and re9uirements of the e2isting system or situation and for determining the operating characteristics of the system. S3&1#: This Document plays a vital role in the development life cycle B D6!D and it describes the complete re9uirement of the system. 't is meant for use by the developers and will be the basic during testing phase. 0ny changes made to the re9uirements in the future will have to go through formal change approval process. DE=ELOPERS RESPONSIBILITIES O=ER=IE The developer is responsible for3 Developing the system* which meets the ; and solving all the re9uirements of the systemF Demonstrating the system and installing the system at client,s location after the acceptance testing is successful. ubmitting the re9uired user manual describing the system interfaces to work on it and also the documents of the system. !onducting any user training that might be needed for using the system. 1aintaining the system for a period of one year after installation. :

$ %< $

4.1. FUNCTIONAL RE5UIREMENTS:

OUTPUT DESIGN Outputs from computer systems are re9uired primarily to communicate the results of processing to users. They are also used to provides a permanent copy of the results for later consultation. The various types of outputs in general are3 .2ternal Outputs* whose destination is outside the organization. 'nternal Outputs whose destination is with in organization and they are the :ser8s main interface with the computer. Operational outputs whose use is purely with in the computer department. 'nterface outputs* which involve the user in communicating directly with

OUTPUT DEFINITION The outputs should be defined in terms of the following points3 Type of the output !ontent of the output &ormat of the output 6ocation of the output &re9uency of the output "olume of the output e9uence of the output 't is not always desirable to print or display data as it is held on a computer. 't should be decided as which form of the output is the most suitable. &or .2ample )ill decimal points need to be inserted hould leading zeros be suppressed.

$ %= $

O+"1+" M#'i!: 'n the ne2t stage it is to be decided that which medium is the most appropriate for the output. The main considerations when deciding about the output media are3 The suitability for the device to the particular application. The need for a hard copy. The response time re9uired. The location of the users The software and hardware available.

Jeeping in view the above description the project is to have outputs mainly coming under the category of internal outputs. The main outputs desired according to the re9uirement specification are3 The outputs were needed to be generated as a hot copy and as well as 9ueries to be viewed on the screen. Jeeping in view these outputs* the format for the output is taken from the outputs* which are currently being obtained after manual processing. The standard printer is to be used as output media for hard copies. INPUT DESIGN 'nput design is a part of overall system design. The main objective during the input design is as given below3 To produce a cost$effective method of input. To achive the highest possible level of accuracy. To ensure that the input is acceptable and understood by the user.

INPUT STAGES: The main input stages can be listed as below3 Data recording Data transcription Data conversion

$ %@ $

Data verification Data control Data transmission Data validation Data correction

INPUT TYPES: 't is necessary to determine the various types of inputs. 'nputs can be categorized as follows3 .2ternal inputs* which are prime inputs for the system. 'nternal inputs* which are user communications with the system. Operational* which are computer department8s communications to the systemF 'nteractive* which are inputs entered during a dialogue.

INPUT MEDIA: 0t this stage choice has to be made about the input media. To conclude about the input media consideration has to be given toK Type of input &le2ibility of format peed 0ccuracy "erification methods ;ejection rates .ase of correction torage and handling re9uirements ecurity .asy to use Portability Jeeping in view the above description of the input types and input media* it can be said that most of the inputs are of the form of internal and interactive. 0s

$ %5 $

'nput data is to be the directly keyed in by the user* the keyboard can be considered to be the most suitable input device.

ERROR A=OIDANCE 0t this stage care is to be taken to ensure that input data remains accurate form the stage at which it is recorded upto the stage in which the data is accepted by the system. This can be achieved only by means of careful control each time the data is handled. ERROR DETECTION .ven though every effort is make to avoid the occurrence of errors* still a small proportion of errors is always likely to occur* these types of errors can be discovered by using validations to check the input data. DATA =ALIDATION Procedures are designed to detect errors in data at a lower level of detail. Data validations have been included in the system in almost every area where there is a possibility for the user to commit errors. The system will not accept invalid data. )henever an invalid data is keyed in* the system immediately prompts the user and the user has to again key in the data and the system will accept the data only if the data is correct. "alidations have been included where necessary. The system is designed to be a user friendly one. 'n other words the system has been designed to communicate effectively with the user. The system has been designed with pop up menus. USER INTERFACE DESIGN 't is essential to consult the system users and discuss their needs while designing the user interface3 USER INTERFACE SYSTEMS CAN BE BROADLY CLASIFIED AS: %. :ser initiated interface the user is in charge* controlling the progress of the user#computer dialogue. 'n the computer$initiated interface* the computer selects the ne2t stage in the interaction. -. !omputer initiated interfaces $ %A $

'n the computer initiated interfaces the computer guides the progress of the user#computer dialogue. 'nformation is displayed and the user response of the computer takes action or displays further information. USER>INITIATED INTERGFACES :ser initiated interfaces fall into tow appro2imate classes3 %. !ommand driven interfaces3 'n this type of interface the user inputs commands or 9ueries which are interpreted by the computer. -. &orms oriented interface3 The user calls up an image of the form to his#her screen and fills in the form. The forms oriented interface is chosen because it is the best choice. COMPUTER4INITIATED INTERFACES The following computer L initiated interfaces were used3 %. The menu system for the user is presented with a list of alternatives and the user chooses oneK of alternatives. -. Euestions L answer type dialog system where the computer asks 9uestion and takes action based on the basis of the users reply. ;ight from the start the system is going to be menu driven* the opening menu displays the available options. !hoosing one option gives another popup menu with more options. 'n this way every option leads the users to data entry form where the user can key in the data. ERROR MESSAGE DESIGN: The design of error messages is an important part of the user interface design. 0s user is bound to commit some errors or other while designing a system the system should be designed to be helpful by providing the user with information regarding the error he#she has committed. This application must be able to produce output at different modules for different inputs.

$ %G $

$ -4 $

4.2. PERFORMANCE RE5UIREMENTS

Performance is measured in terms of the output provided by the application. ;e9uirement specification plays an important part in the analysis of a system. Only when the re9uirement specifications are properly given* it is possible to design a system* which will fit into re9uired environment. 't rests largely in the part of the users of the e2isting system to give the re9uirement specifications because they are the people who finally use the system. This is because the re9uirements have to be known during the initial stages so that the system can be designed according to those re9uirements. 't is very difficult to change the system once it has been designed and on the other hand designing a system* which does not cater to the re9uirements of the user* is of no use. The re9uirement specification for any system can be broadly stated as given below3 The system should be able to interface with the e2isting system The system should be accurate The system should be better than the e2isting system

The e2isting system is completely dependent on the user to perform all the duties.

$ -% $

6. SELECTED SOFT
6.1. INTRODUCTION TO .NET F$!*#?&$0

ARE

The .7.T &ramework is a new computing platform that simplifies application development in the highly distributed environment of the 'nternet. The .7.T &ramework is designed to fulfill the following objectives3

To provide a consistent object$oriented programming environment whether object code is stored and e2ecuted locally* e2ecuted locally but 'nternet$distributed* or e2ecuted remotely.

To provide a code$e2ecution environment that minimizes software deployment and versioning conflicts. To provide a code$e2ecution environment that guarantees safe e2ecution of code* including code created by an unknown or semi$trusted third party. To provide a code$e2ecution environment that eliminates the performance problems of scripted or interpreted environments. To make the developer e2perience consistent across widely varying types of applications* such as )indows$based applications and )eb$based applications. To build all communication on industry standards to ensure that code based on the .7.T &ramework can integrate with any other code.

The .7.T &ramework has two main components3 the common language runtime and the .7.T &ramework class library. The common language runtime is the foundation of the .7.T &ramework. Mou can think of the runtime as an agent that manages code at e2ecution time* providing core services such as memory management* thread management* and ;emoting* while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. 'n fact* the concept of code management is a fundamental principle of the runtime. !ode that targets the runtime is known as managed code* while code that does not target the runtime is known as unmanaged code. The class library* the other main component of the .7.T &ramework* is a comprehensive* object$oriented collection of reusable types that you can use to develop applications ranging from traditional command$line or graphical

$ -- $

user interface B?:'D applications to applications based on the latest innovations provided by 0 P.7.T* such as )eb &orms and C16 )eb services. The .7.T &ramework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the e2ecution of managed code* thereby creating a software environment that can e2ploit both managed and unmanaged features. The .7.T &ramework not only provides several runtime hosts* but also supports the development of third$party runtime hosts. &or e2ample* 0 P.7.T hosts the runtime to provide a scalable* server$side environment for managed code. 0 P.7.T works directly with the runtime to enable )eb &orms applications and C16 )eb services* both of which are discussed later in this topic. 'nternet .2plorer is an e2ample of an unmanaged application that hosts the runtime Bin the form of a 1'1. type e2tensionD. :sing 'nternet .2plorer to host the runtime enables you to embed managed components or )indows &orms controls in /T16 documents. /osting the runtime in this way makes managed mobile code Bsimilar to 1icrosoftN 0ctiveCN controlsD possible* but with significant improvements that only managed code can offer* such as semi$trusted e2ecution and secure isolated file storage. The following illustration shows the relationship of the common language runtime and the class library to your applications and to the overall system. The illustration also shows how managed code operates within a larger architecture. FEATURES OF THE COMMON LANGUAGE RUNTIME The common language runtime manages memory* thread e2ecution* code e2ecution* code safety verification* compilation* and other system services. These features are intrinsic to the managed code that runs on the common language runtime. )ith regards to security* managed components are awarded varying degrees of trust* depending on a number of factors that include their origin Bsuch as the 'nternet* enterprise network* or local computerD. This means that a managed component might or might not be able to perform file$access operations* registry$

$ -( $

access operations* or other sensitive functions* even if it is being used in the same active application. The runtime enforces code access security. &or e2ample* users can trust that an e2ecutable embedded in a )eb page can play an animation on screen or sing a song* but cannot access their personal data* file system* or network. The security features of the runtime thus enable legitimate 'nternet$deployed software to be e2ceptionally featuring rich. The runtime also enforces code robustness by implementing a strict type$ and code$verification infrastructure called the common type system B!T D. The !T ensures that all managed code is self$describing. The various 1icrosoft and third$ party language compilers ?enerate managed code that conforms to the !T . This means that managed code can consume other managed types and instances* while strictly enforcing type fidelity and type safety. 'n addition* the managed environment of the runtime eliminates many common software issues. &or e2ample* the runtime automatically handles object layout and manages references to objects* releasing them when they are no longer being used. This automatic memory management resolves the two most common application errors* memory leaks and invalid memory references. The runtime also accelerates developer productivity. &or e2ample* 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. 0ny compiler vendor who chooses to target the runtime can do so. 6anguage compilers that target the .7.T &ramework make the features of the .7.T &ramework available to e2isting code written in that language* greatly easing the migration process for e2isting applications. )hile the runtime is designed for the software of the future* it also supports software of today and yesterday. 'nteroperability between managed and unmanaged code enables developers to continue to use necessary !O1 components and D66s. The runtime is designed to enhance performance. 0lthough the common language runtime provides many standard runtime services* managed code is never interpreted. 0 feature called just$in$time BJ'TD compiling enables all managed code to run in the native machine language of the system on which it is e2ecuting.

$ -< $

1eanwhile* the memory manager removes the possibilities of fragmented memory and increases memory locality$of$reference to further increase performance. &inally* the runtime can be hosted by high$performance* server$side applications* such as 1icrosoftN E6 erverO and 'nternet 'nformation ervices B'' D. This infrastructure enables you to use managed code to write your business logic* while still enjoying the superior performance of the industry,s best enterprise servers that support runtime hosting. .NET FRAME OR7 CLASS LIBRARY

The .7.T &ramework class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is object oriented* providing types from which your own managed code can derive functionality. This not only makes the .7.T &ramework types easy to use* but also reduces the time associated with learning new features of the .7.T &ramework. 'n addition* third$party components can integrate seamlessly with classes in the .7.T &ramework. &or e2ample* the .7.T &ramework collection classes implement a set of interfaces that you can use to develop your own collection classes. Mour collection classes will blend seamlessly with the classes in the .7.T &ramework. 0s you would e2pect from an object$oriented class library* the .7.T &ramework types enable you to accomplish a range of common programming tasks* including tasks such as string management* data collection* database connectivity* and file access. 'n addition to these common tasks* the class library includes types that support a variety of specialized development scenarios. &or e2ample* you can use the .7.T &ramework to develop the following types of applications and services3

!onsole applications. cripted or hosted applications. )indows ?:' applications B)indows &ormsD. 0 P.7.T applications. C16 )eb services. )indows services.

$ -= $

&or e2ample* the )indows &orms classes are a comprehensive set of reusable types that vastly simplify )indows ?:' development. 'f you write an 0 P.7.T )eb &orm application* you can use the )eb &orms classes.

6.2 ACTI=E SER=ER PAGES.NET

0 P.7.T is a programming framework built on the common language runtime that can be used on a server to build powerful )eb applications. 0 P.7.T offers several important advantages over previous )eb development models3 E-)!-3#' P#$2&$*!-3#. 0 P.7.T is compiled common language runtime code running on the server. :nlike its interpreted predecessors* 0 P.7.T can take advantage of early binding* just$in$time compilation* native optimization* and caching services right out of the bo2. This amounts to dramatically better performance before you ever write a line of code. &$%'4C%!,, T&&% S+11&$". The 0 P.7.T framework is complemented by a rich toolbo2 and designer in the "isual tudio integrated development environment. )M ')M? editing* drag$and$drop server controls* and automatic deployment are just a few of the features this powerful tool provides. P&?#$ !-' F%#@i/i%i"<. +ecause 0 P.7.T is based on the common language runtime* the power and fle2ibility of that entire platform is available to )eb application developers. The .7.T &ramework class library* 1essaging* and Data 0ccess solutions are all seamlessly accessible from the )eb. 0 P.7.T is also language$independent* so you can choose the language that best applies to your application or partition your application across many languages. &urther* common language runtime interoperability guarantees that your e2isting investment in !O1$based development is preserved when migrating to 0 P.7.T. Si*1%i3i"<. 0 P.7.T makes it easy to perform common tasks* from simple form submission and client authentication to deployment and site configuration. &or e2ample* the 0 P.7.T page framework allows you to build user interfaces that cleanly separate application logic from presentation code and to handle events in a simple* "isual +asic $ like forms processing model. 0dditionally* the common language runtime simplifies development* with managed code services such as automatic reference counting and garbage collection. M!-!g#!/i%i"<. 0 P.7.T employs a te2t$based* hierarchical configuration system* which simplifies applying settings to your server environment and )eb

$ -@ $

applications. +ecause configuration information is stored as plain te2t* new settings may be applied without the aid of local administration tools. This Hzero local administrationH philosophy e2tends to deploying 0 P.7.T &ramework applications as well. 0n 0 P.7.T &ramework application is deployed to a server simply by copying the necessary files to the server. 7o server restart is re9uired* even to deploy or replace running compiled code. S3!%!/i%i"< !-' A.!i%!/i%i"<. 0 P.7.T has been designed with scalability in mind* with features specifically tailored to improve performance in clustered and multiprocessor environments. &urther* processes are closely monitored and managed by the 0 P.7.T runtime* so that if one misbehaves Bleaks* deadlocksD* a new process can be created in its place* which helps keep your application constantly available to handle re9uests. C+,"&*iA!/i%i"< !-' E@"#-,i/i%i"<. 0 P.7.T delivers a well$factored architecture that allows developers to Hplug$inH their code at the appropriate level. 'n fact* it is possible to e2tend or replace any subcomponent of the 0 P.7.T runtime with your own custom$written component. 'mplementing custom authentication or state services has never been easier. S#3+$i"<. )ith built in )indows authentication and per$application configuration* you can be assured that your applications are secure. LANGUAGE SUPPORT The 1icrosoft .7.T Platform currently offers built$in support for three languages3 !P* "isual +asic* and J cript. HAT IS ASP.NET EB FORMSB

The 0 P.7.T )eb &orms page framework is a scalable common language runtime programming model that can be used on the server to dynamically generate )eb pages. 'ntended as a logical evolution of 0 P B0 P.7.T provides synta2 compatibility with e2isting pagesD* the 0 P.7.T )eb &orms framework has been specifically designed to address a number of key deficiencies in the previous model. 'n particular* it provides3

$ -5 $

The ability to create and use reusable :' controls that can encapsulate common functionality and thus reduce the amount of code that a page developer has to write.

The ability for developers to cleanly structure their page logic in an orderly fashion Bnot Hspaghetti codeHD. The ability for development tools to provide strong )M ')M? design support for pages Be2isting 0 P code is opa9ue to toolsD. 0 P.7.T )eb &orms pages are te2t files with an .asp2 file name e2tension.

They can be deployed throughout an '' virtual root directory tree. )hen a browser client re9uests .asp2 resources* the 0 P.7.T runtime parses and compiles the target file into a .7.T &ramework class. This class can then be used to dynamically process incoming re9uests. B7ote that the .asp2 file is compiled only the first time it is accessedK the compiled type instance is then reused across multiple re9uestsD. 0n 0 P.7.T page can be created simply by taking an e2isting /T16 file and changing its file name e2tension to .asp2 Bno modification of code is re9uiredD. &or e2ample* the following sample demonstrates a simple /T16 page that collects a user,s name and category preference and then performs a form postback to the originating page when a button is clicked3 0 P.7.T provides synta2 compatibility with e2isting 0 P pages. This includes support for QR RS code render blocks that can be intermi2ed with /T16 content within an .asp2 file. These code blocks e2ecute in a top$down manner at page render time. CODE4BEHIND EB FORMS

0 P.7.T supports two methods of authoring dynamic pages. The first is the method shown in the preceding samples* where the page code is physically declared within the originating .asp2 file. 0n alternative approach$$known as the code$behind method$$enables the page code to be more cleanly separated from the /T16 content into an entirely separate file. INTRODUCTION TO ASP.NET SER=ER CONTROLS

$ -A $

'n addition to Bor instead ofD using QR RS code blocks to program dynamic content* 0 P.7.T page developers can use 0 P.7.T server controls to program )eb pages. erver controls are declared within an .asp2 file using custom tags or intrinsic /T16 tags that contain a $+-!"CD,#$.#$D attributes value. 'ntrinsic /T16 tags are handled by one of the controls in the S<,"#*. type of S<,"#*. #/.UI.H"*%C&-"$&%,.H"*%G#-#$i3C&-"$&%. #/.UI.H"*%C&-"$&%, namespace. 0ny tag that doesn,t e2plicitly map to one of the controls is assigned the erver controls automatically maintain any client$entered values between round trips to the server. This control state is not stored on the server Bit is instead stored within an Ei-1+" "<1#CD)i''#-DF form field that is round$tripped between re9uestsD. 7ote also that no client$side script is re9uired. 'n addition to supporting standard /T16 input controls* 0 P.7.T enables developers to utilize richer custom controls on their pages. &or e2ample* the following sample demonstrates how the E!,1:!'$&"!"&$F control can be used to dynamically display rotating ads on a page. %. 0 P.7.T )eb &orms provide an easy and powerful way to build dynamic )eb :'. -. 0 P.7.T )eb &orms pages can target any browser client Bthere are no script library or cookie re9uirementsD. (. 0 P.7.T )eb &orms pages provide synta2 compatibility with e2isting 0 P pages. <. 0 P.7.T server controls provide an easy way to encapsulate common functionality. =. 0 P.7.T ships with <= built$in server controls. Developers can also use controls built by third parties. @. 0 P.7.T server controls can automatically project both uplevel and downlevel /T16. 5. 0 P.7.T templates provide an easy way to customize the look and feel of list server controls. A. 0 P.7.T validation controls provide an easy way to do declarative client or server data validation.

$ -G $

6.3 S5L SER=ER

0 database management* or D+1 * gives the user access to their data and helps them transform the data into information. uch database management systems include d+ase* parado2* '1 * E6 erver and E6 erver. These systems allow users to create* update and e2tract information from their database. 0 database is a structured collection of data. Data refers to the characteristics of people* things and events. E6 E6 erver stores each data item in its own fields. 'n erver* the fields relating to a particular person* thing or event are bundled

together to form a single complete unit of data* called a record Bit can also be referred to as raw or an occurrenceD. .ach record is made up of a number of fields. 7o two fields in a record can have the same field name. During an E6 erver Database design project* the analysis of your business needs identifies all the fields or attributes of interest. 'f your business needs change over time* you define any additional fields or change the definition of e2isting fields. S5L SER=ER TABLES E6 erver stores records relating to each other in a table. Different tables are created for the various groups of information. ;elated tables are grouped together to form a database. PRIMARY 7EY .very table in E6 erver has a field or a combination of fields that uni9uely identifies each record in the table. The :ni9ue identifier is called the Primary Jey* or simply the Jey. The primary key provides the means to distinguish one record from all other in a table. 't allows the user and the database system to identify* locate and refer to one particular record in the database. RELATIONAL DATABASE ometimes all the information of interest to a business operation can be stored in one table. E6 erver makes it very easy to link the data in multiple tables. 1atching an employee to the department in which they work is one e2ample. This is what makes E6 erver a relational database management system* or ;D+1 . 't

$ (4 $

stores data in two or more tables and enables you to define relationships between the table and enables you to define relationships between the tables. FOREIGN 7EY )hen a field is one table matches the primary key of another field is referred to as a foreign key. 0 foreign key is a field or a group of fields in one table whose values match those of the primary key of another table. REFERENTIAL INTEGRITY 7ot only does E6 erver allow you to link multiple tables* it also maintains consistency between them. .nsuring that the data among related tables is correctly matched is referred to as maintaining referential integrity. DATA ABSTRACTION 0 major purpose of a database system is to provide users with an abstract view of the data. This system hides certain details of how the data is stored and maintained. Data abstraction is divided into three levels. P)<,i3!% %#.#%3 This is the lowest level of abstraction at which one describes how the data are actually stored. C&-3#1"+!% L#.#%3 0t this level of database abstraction all the attributed and what data are actually stored is described and entries and relationship among them. =i#? %#.#%3 This is the highest level of abstraction at which one describes only part of the database. AD=ANTAGES OF RDBMS ;edundancy can be avoided 'nconsistency can be eliminated Data can be hared tandards can be enforced ecurity restrictions ca be applied 'ntegrity can be maintained $ (% $

!onflicting re9uirements can be balanced Data independence can be achieved. 0 significant disadvantage of the D+1 system is cost. 'n addition to the cost

DISAD=ANTAGES OF DBMS of purchasing of developing the software* the hardware has to be upgraded to allow for the e2tensive programs and the workspace re9uired for their e2ecution and storage. )hile centralization reduces duplication* the lack of duplication re9uires that the database be ade9uately backed up so that in case of failure the data can be recovered. FEATURES OF S5L SER=ER :RDBMSD E6 .;".; is one of the leading database management systems BD+1 D because it is the only Database that meets the uncompromising re9uirements of today8s most demanding information systems. systems BD even application that re9uire simultaneous D &rom comple2 decision support D to the most rigorous online transaction processing BO6TPD application* and O6TP access to the same critical

data* E6 erver leads the industry in both performance and capability E6 .;".; is a truly portable* distributed* and open D+1 that delivers

unmatched performance* continuous operation and support for every database. E6 .;".; ;D+1 is high performance fault tolerant D+1 which is specially designed for online transactions processing and for handling large database application. E6 .;".; with transactions processing option offers two features which

contribute to very high level of transaction processing throughput* which are

$ (- $

8. SYSTEM DESIGN
8.1. INTRODUCTION
oftware design sits at the technical kernel of the software engineering process and is applied regardless of the development paradigm and area of application. Design is the first step in the development phase for any engineered product or system. The designer8s goal is to produce a model or representation of an entity that will later be built. +eginning* once system re9uirement have been specified and analyzed* system design is the first of the three technical activities $design* code and test that is re9uired to build and verify software. The importance can be stated with a single word TEualityU. Design is the place where 9uality is fostered in software development. Design provides us with representations of software that can assess for 9uality. Design is the only way that we can accurately translate a customer8s view into a finished software product or system. oftware design serves as a foundation for all the software engineering steps that follow. )ithout a strong design we risk building an unstable system L one that will be difficult to test* one whose 9uality cannot be assessed until the last stage. During design* progressive refinement of data structure* program structure* and procedural details are developed reviewed and documented. ystem design can be viewed from either technical or project management perspective. &rom the technical point of view* design is comprised of four activities L architectural design* data structure design* interface design and procedural design.

$ (( $

8.2. NORMALIZATION
't is a process of converting a relation to a standard form. The process is used to handle the problems that can arise due to data redundancy i.e. repetition of data in the database* maintain data integrity as well as handling problems that can arise due to insertion* updation* deletion anomalies. Decomposing is the process of splitting relations into multiple relations to eliminate anomalies and maintain anomalies and maintain data integrity. To do this we use normal forms or rules for structuring relation. I-,#$"i&- !-&*!%<3 'nability to add data to the database due to absence of other data. D#%#"i&- !-&*!%<3 :nintended loss of data due to deletion of other data. U1'!"# !-&*!%<3 Data inconsistency resulting from data redundancy and partial update N&$*!% F&$*,3 These are the rules for structuring relations that eliminate anomalies. FIRST NORMAL FORM3 0 relation is said to be in first normal form if the values in the relation are atomic for every attribute in the relation. +y this we mean simply that no attribute value can be a set of values or* as it is sometimes e2pressed* a repeating group. SECOND NORMAL FORM3 0 relation is said to be in second 7ormal form is it is in first normal form and it should satisfy any one of the following rules. %D Primary key is a not a composite primary key -D 7o non key attributes are present (D .very non key attribute is fully functionally dependent on full set of primary key. THIRD NORMAL FORM3 0 relation is said to be in third normal form if their e2its no transitive dependencies. T$!-,i"i.# D#1#-'#-3<3 'f two non key attributes depend on each other as well as on the primary key then they are said to be transitively dependent. The above normalization principles were applied to decompose the data in multiple tables thereby making the data to be maintained in a consistent state.

$ (< $

8.4. DATA FLO

DIAGRAMS

0 data flow diagram is graphical tool used to describe and analyze movement of data through a system. These are the central tool and the basis from which the other components are developed. The transformation of data from input to output* through processed* may be described logically and independently of physical components associated with the system. These are known as the logical data flow diagrams. The physical data flow diagrams show the actual implements and movement of data between people* departments and workstations. 0 full description of a system actually consists of a set of data flow diagrams. :sing two familiar notations Mourdon* ?ane and arson notation develops the data flow diagrams. .ach component in a D&D is labeled with a descriptive name. Process is further identified with a number that will be used for identification purpose. The development of D&D8 is done in several levels. .ach process in lower level diagrams can be broken down into a more detailed D&D in the ne2t level. The lop$level diagram is often called conte2t diagram. 't consists a single process bit* which plays vital role in studying the current system. The process in the conte2t level diagram is e2ploded into other process at the first level D&D. The idea behind the e2plosion of a process into more process is that understanding at one level of detail is e2ploded into greater detail at the ne2t level. This is done until further e2plosion is necessary and an ade9uate amount of detail is described for analyst to understand the process. 6arry !onstantine first developed the D&D as a way of e2pressing system re9uirements in a graphical from* this lead to the modular design. 0 D&D is also known as a Tbubble !hartU has the purpose of clarifying system re9uirements and identifying major transformations that will become programs in system design. series of bubbles joined by data flows in the system. o it is the starting point of the design to the lowest level of detail. 0 D&D consists of a

$ (= $

DFD SYMBOLS: 'n the D&D* there are four symbols %. 0 s9uare defines a sourceBoriginatorD or destination of system data -. 0n arrow identifies data flow. 't is the pipeline through which the information flows (. 0 circle or a bubble represents a process that transforms incoming data flow into outgoing data flows. <. 0n open rectangle is a data store* data at rest or a temporary repository of data

Process that transforms data flow.

ource or Destination of data Data flow Data tore

CONSTRUCTING A DFD: everal rules of thumb are used in drawing D&D8 3 %. Process should be named and numbered for an easy reference. .ach name should be representative of the process. -. The direction of flow is from top to bottom and from left to right. Data traditionally flow from source to the destination although they may flow back to the source. One way to indicate this is to draw long flow line back to a source. 0n alternative way is to repeat the source symbol as a destination. more than once in the D&D it is marked with a short diagonal. (. )hen a process is e2ploded into lower level details* they are numbered. <. The names of data stores and destinations are written in capital letters. Process and dataflow names have the first letter of each work capitalized ince it is used

$ (@ $

0 D&D typically shows the minimum contents of data store. .ach data store should contain all the data elements that flow in and out. Euestionnaires should contain all the data elements that flow in and out. 1issing interfaces redundancies and like is then accounted for often through interviews.

DATA FLO %D 0 Data &low has only one direction of flow between symbols. 't may flow in both directions between a process and a data store to show a read before an update. The later is usually indicated however by two separate arrows since these happen at different type. -D 0 join in D&D means that e2actly the same data comes from any of two or more different processes data store or sink to a common location. (D 0 data flow cannot go directly back to the same process it leads. There must be atleast one other process that handles the data flow produce some other data flow returns the original data into the beginning process. <D 0 Data flow to a data store means update Bdelete or changeD. =D 0 data &low from a data store means retrieve or use. 0 data flow has a noun phrase label more than one data flow noun phrase can appear on a single arrow as long as all of the flows on the same arrow move together as one package.

$ (5 $

1," L#.#% DFD(,

DFD F&$ N#? J&/ S##0#$ C$#!"i&-

Job eeker Details

;egistratio n Details

'nsert 7ew Job eeker

"erify Data

!heck for ;egistration Details

"erify Data

Insert

Job eeker Details

$ (A $

DFD F&$ N#? J&/ S##0#$ C$#!"i&-

Job Provider Details

;egistratio n Details

'nsert 7ew Job Provider

"erify Data

!heck for ;egistration Details

"erify Data

Insert

Job Provider

$ (G $

DFD F&$ N#? J&/ S#!$3) C$#!"i&-

Job eeker Details

;egistration Details

earch Job Details

'nsert 7ew Job eeker

"erify Data

!heck for ;egistration

!heck &or Job

"erify Data "erify Data

Insert

Job eeker Det

$ <4 $

nd

6evel D&D8s

DFD For New Recruitment Creation

Job eeker Details

Designation Type Details

Job Provider Details

'nsert 7ew Job eeker

!heck for Designation "erify Data "erify Data "erify Data

!heck for Job Provider !heck for Job eeker 'nfo

!heck for Type

"erify Data

"erify Data

!heck for tatus

"erify Data

Job eeker Details

Job Provider tatus Details

Job eeker Details

$ <% $

(rd 6evel D&D8

DFD For New Recruitment Creation

Job Provider Details

Job eeker Details

Designation Type Details

;e9uest for new Job eeker

?enerate .mp$'d BD

"alidate Desg$'d BD

"alidate Prod$'d BD

!ommit BD

"alidate Prod$ tatus$'D BD

"alidate Job$ eek$'d BD

Database :pdated Job eeker Details

Job Provider tatus Details

Job eeker status Details

$ <- $

8.6. DATA DICTONARY

0fter carefully understanding the re9uirements of the client the the entire data storage re9uirements are divided into tables. The below tables are normalized to avoid any anomalies during the course of data entry.

!ity Details

!ountry Details

.2perience Detail

&unctional 0rea

$ <( $

Job Opening Detail

Jobseeker ;esponse to ;ecruiter

Job Type Detail

6ocation 1aster

Eualification

;ecruiter 0ccount Details

$ << $

;ecruiter Organization Details

;ecruiter ;esponse to Jobseeker

kill 1aster

tate detail

tudent Detail

$ <= $

0dmin 6ogin

Jobseeker +ackground Details

!ontact Details

Jobseeker Job Details

$ <@ $

Jobseeker ;egistration

Jobseeker ;esume

Jobseeker Technical Details

$ <5 $

OUTPUT SCREENS

$ <A $

$ <G $

$ =4 $

$ =% $

$ =- $

$ =( $

$ =< $

$ == $

$ =@ $

$ =5 $

$ =A $

$ =G $

$ @4 $

$ @% $

G. SYSTEM TESTING AND IMPLEMENTATION

G.1. INTRODUCTION oftware testing is a critical element of software 9uality assurance and represents the ultimate review of specification* design and coding. 'n fact* testing is the one step in the software engineering process that could be viewed as destructive rather than constructive. 0 strategy for software testing integrates software test case design methods into a well$planned series of steps that result in the successful construction of software. Testing is the set of activities that can be planned in advance and conducted systematically. The underlying motivation of program testing is to affirm software 9uality with methods that can economically and effectively apply to both strategic to both large and small$scale systems. G.2. STRATEGIC APPROACH TO SOFT ARE TESTING

The software engineering process can be viewed as a spiral. 'nitially system engineering defines the role of software and leads to software re9uirement analysis where the information domain* functions* behavior* performance* constraints and validation criteria for software are established. 1oving inward along the spiral* we come to design and finally to coding. To develop computer software we spiral in along streamlines that decrease the level of abstraction on each turn. 0 strategy for software testing may also be viewed in the conte2t of the spiral. :nit testing begins at the verte2 of the spiral and concentrates on each unit of the software as implemented in source code. Testing progress by moving outward along the spiral to integration testing* where the focus is on the design and the construction of the software architecture. Talking another turn on outward on the spiral we encounter validation testing where re9uirements established as part of software re9uirements analysis are validated against the software that has been constructed. &inally we arrive at system testing* where the software and other system elements are tested as a whole.

$ @- $

:7'T T. T'7?

1OD:6. T. T'7?

Component Testing

:+$ M T.1 T. '7?

M T.1 T. T'7?

Integration Testing

User Testing
G.3. U-i" T#,"i-g

0!!.PT07!. T. T'7?

:nit testing focuses verification effort on the smallest unit of software design* the module. The unit testing we have is white bo2 oriented and some modules the steps are conducted in parallel. 1. HITE BOX TESTING

This type of testing ensures that 0ll independent paths have been e2ercised at least once 0ll logical decisions have been e2ercised on their true and false sides 0ll loops are e2ecuted at their boundaries and within their operational bounds 0ll internal data structures have been e2ercised to assure their validity.

To follow the concept of white bo2 testing we have tested each form .we have created independently to verify that Data flow is correct* 0ll conditions are e2ercised to check their validity* 0ll loops are e2ecuted on their boundaries.

$ @( $

2. BASIC PATH TESTING .stablished techni9ue of flow graph with !yclomatic comple2ity was used to derive test cases for all the functions. The main steps in deriving test cases were3 :se the design of the code and draw correspondent flow graph. Determine the !yclomatic comple2ity of resultant flow graph* using formula3 "B?DV.$7W- or "B?DVPW% or "B?DV7umber Of ;egions )here "B?D is !yclomatic comple2ity* . is the number of edges* 7 is the number of flow graph nodes* P is the number of predicate nodes. Determine the basis of set of linearly independent paths.

3. CONDITIONAL TESTING 'n this part of the testing each of the conditions were tested to both true and false aspects. 0nd all the resulting paths were tested. o that each path that may be generate on particular condition is traced to uncover any possible errors. 4. DATA FLO TESTING

This type of testing selects the path of the program according to the location of definition and use of variables. This kind of testing was used only when some local variable were declared. The definition-use chain method was used in this type of testing. These were particularly useful in nested statements. 6. LOOP TESTING 'n this type of testing all the loops are tested to all the limits possible. The following e2ercise was adopted for all loops3 0ll the loops were tested at their limits* just above them and just below them. 0ll the loops were skipped at least once. &or nested loops test the inner most loop first and then work outwards. $ @< $

&or concatenated loops the values of dependent loops were set with the help of connected loop. :nstructured loops were resolved into nested loops or concatenated loops and tested as above.

.ach unit has been separately tested by the development team itself and all the input have been validated.

$ @= $

H. SYSTEM SECURITY
H.1. I-"$&'+3"i&The protection of computer based resources that includes hardware* software* data* procedures and people against unauthorized use or natural Disaster is known as ystem ecurity. ystem ecurity can be divided into four related issues3 ecurity 'ntegrity Privacy !onfidentiality

SYSTEM SECURITY refers to the technical innovations and procedures applied to the hardware and operation systems to protect against deliberate or accidental damage from a defined threat. DATA SECURITY is the protection of data from loss* disclosure* modification and destruction. SYSTEM INTEGRITY refers to the power functioning of hardware and programs* appropriate physical security and safety against e2ternal threats such as eavesdropping and wiretapping. PRI=ACY defines the rights of the user or organizations to determine what information they are willing to share with or accept from others and how the organization can be protected against unwelcome* unfair or e2cessive dissemination of information about it. CONFIDENTIALITY is a special status given to sensitive information in a database to minimize the possible invasion of privacy. 't is an attribute of information that characterizes its need for protection.

$ @@ $

H.2. SECURITY IN SOFT

ARE

ystem security refers to various validations on data in form of checks and controls to avoid the system from failing. 't is always important to ensure that only valid data is entered and only valid operations are performed on the system. The system employees two types of checks and controls3 CLIENT SIDE =ALIDATION "arious client side validations are used to ensure on the client side that only valid data is entered. !lient side validation saves server time and load to handle invalid data. ome checks imposed are3 "+ cript in used to ensure those re9uired fields are filled with suitable data only. 1a2imum lengths of the fields of the forms are appropriately defined. &orms cannot be submitted without filling up the mandatory data so that manual mistakes of submitting empty fields that are mandatory can be sorted out at the client side to save the server time and load. Tab$inde2es are set according to the need and taking into account the ease of user while working with the system.

SER=ER SIDE =ALIDATION ome checks cannot be applied at client side. erver side checks are necessary to save the system from failing and intimating the user that some invalid operation has been performed or the performed operation is restricted. ome of the server side checks imposed is3 erver side constraint has been imposed to check for the validity of primary key and foreign key. 0 primary key value cannot be duplicated. 0ny attempt to duplicate the primary value results into a message intimating the user about those values through the forms using foreign key can be updated only of the e2isting foreign key values. :ser is intimating through appropriate messages about the successful operations or e2ceptions occurring at server side.

$ @5 $

"arious 0ccess !ontrol 1echanisms have been built so that one user may not agitate upon another. 0ccess permissions to various types of users are controlled according to the organizational structure. Only permitted users can log on to the system and can have access according to their category. :ser$ name* passwords and permissions are controlled o the server side.

:sing server side validation* constraints on several restricted operations are imposed.

$ @A $

1I. CONCLUSION
't has been a great pleasure for me to work on this e2citing and challenging project. This project proved good for me as it provided practical knowledge of not only programming in 0 P.7.T and "+.7.T web based application and no some e2tent )indows 0pplication and E6 erver* but also about all handling procedure related with JO-%i-# J&/ P&$"!%K. 't also provides knowledge about the latest technology used in developing web enabled application and client server technology that will be great demand in future. This will provide better opportunities and guidance in future in developing projects independently. BENEFITS: The project is identified by the merits of the system offered to the user. The merits of this project are as follows3 $ 't8s a web$enabled project. This project offers user to enter the data through simple and interactive forms. This is very helpful for the client to enter the desired information through so much simplicity. The user is mainly more concerned about the validity of the data* whatever he is entering. There are checks on every stages of any new creation* data entry or updation so that the user cannot enter the invalid data* which can create problems at later date. ometimes the user finds in the later stages of using project that he needs to update some of the information that he entered earlier. There are options for him by which he can update the records. 1oreover there is restriction for his that he cannot change the primary data field. This keeps the validity of the data to longer e2tent. :ser is provided the option of monitoring the records he entered earlier. /e can see the desired records with the variety of options provided by him. &rom every part of the project the user is provided with the links through framing so that he can go from one option of the project to other as per the re9uirement.

$ @G $

This is bound to be simple and very friendly as per the user is concerned. That is* we can sat that the project is user friendly which is one of the primary concerns of any good project. Data storage and retrieval will become faster and easier to maintain because data is stored in a systematic manner and in a single database. Decision making process would be greatly enhanced because of faster processing of information since data collection from information available on computer takes much less time then manual system. 0llocating of sample results becomes much faster because at a time the user can see the records of last years. .asier and faster data transfer through latest technology associated with the computer and communication. Through these features it will increase the efficiency* accuracy and transparency*

LIMITATIONS: The size of the database increases day$by$day* increasing the load on the database back up and data maintenance activity. Training for simple computer operations is necessary for the the system. users working on

$ 54 $

11. SCOPE IN FUTURE ENHANCEMENT

This ystem being web$based and an undertaking of !yber ecurity Division* needs to be thoroughly tested to find out any security gaps. 0 console for the data centre may be made available to allow the personnel to monitor on the sites which were cleared for hosting during a particular period. 1oreover* it is just a beginningK further the system may be utilized in various other types of auditing operation viz. 7etwork auditing or similar process#workflow based applications...

$ 5% $

BIBLIOGRAPHY
FOR .NET INSTALLATION www.support.mircosoft.com FOR DEPLOYMENT AND PAC7ING ON SER=ER www.developer.com www.%=seconds.com FOR S5L www.msdn.microsoft.com FOR ASP.NET www.msdn.microsoft.com#net#9uickstart#aspplus#default.com www.asp.net www.fme2pense.com#9uickstart#aspplus#default.com www.asptoday.com www.aspfree.com www.<guysfromrolla.com#inde2.asp2

$ 5- $