hr information project report[www.students3k.com]

8/10/2019 HR Information Project Report[Www.students3k.com]

1/113

http://students3k.com

able of Contents

able of Contents

Introduction

ntroduction

"Human Resource Information System" is an information system to provide effective control ofsafety functions and employees' compensation and leave records. This system is meant tobe installed at Durgapur Steel Plant DSP!. The development of the system is done at theRD RD#IS!$ Steel %thority of India &imited S%I&!$ Ranchi$ har(hand$ India. This systemis an e)tension to a "Human Resource Information System HRIS!" developed by RD#IS$S%I& for Durgapur Steel Plant.

The system$ basically$ deals *ith areas not considered in HRIS$ such as$ employees+ safetyrelated functions$ leave record and management of gate pass and statutory re,uirements of#ontract &abour #ell #!.

-asically$ It is a userfriendly Human Resource Information System HRIS!. It allo*s theorgani/ation to ta(e advantage of enterprise class HR functionality *ithout the over*helming

e)pense traditionally incurred. It manages the employee information$ so provides an aid tomanager to manage the employees efficiently.

This particular pac(age is meant to revolutioni/e the *ay to manage the human resourcedemands. Time re,uired to search the information *ill be available for planning and headingoff potential problems. The value for benefit that *ill be received is outstanding and *ill helpthe employees of the organisation to a great e)tent.

The 0a1or areas considered by the system can be characterised as

Safety 2unctions

3mployees4 &eave Record 2unction

#ontract &abour #ell #!

The system interacts *ith three different departments5

Safety Department

Personnel Department

2inance Department

The involvement of these department demands proper coordination bet*een them. 2orproper and efficient functioning$ the system interacts *ith these three departments.

The ob1ective of the information system is to provide an efficient handling of manpo*er

resource and (eeping trac( of the accident related information. The system also helps in(eeping the employees4 leave record up to date. The assistance provided by the system canbe 5

3ffective and 3fficient utili/ation of the e)isting man po*er.

0aintenance of accident detail$ analysis and redressal activity.

0anagement of employee's leave records.

http://students3k.com/http://students3k.com/http://students3k.com/http://students3k.com/


2/113


1.1. Organizational BackgroundOrganizational Background

1.1 Company Profile

Steel %uthority of India &imited S%I&! is the leading steelma(ing company in India. It is afully integrated iron and steel ma(er$ producing both basic and special steels for domesticconstruction$ engineering$ po*er$ rail*ay$ automotive and defence industries and for sale ine)port mar(ets.

Ran(ed amongst the top ten public sector companies in India in terms of turnover$ S%I&manufactures and sells a broad range of steel products$ including hot and cold rolled sheetsand coils$ galvanised sheets$ electrical sheets$ structurals$ rail*ay products$ plates$ bars androds$ stainless steel and other alloy steels. S%I& produces iron and steel at four integrated

plants and three special steel plants$ located principally in the eastern and central regions ofIndia and situated close to domestic sources of ra* materials$ including the #ompany's ironore$ limestone and dolomite mines.

S%I&'s *ide range of long and flat steel products is much in demand in the domestic as *ellas the international mar(et. This vital responsibility is carried out by S%I&'s o*n #entral0ar(eting 6rganisation #06! and the International Trade Division. #06 encompasses a*ide net*or( of 78 branch offices and 9: stoc(yards located in ma1or cities and to*nsthroughout India.

;ith technical and managerial e)pertise and (no*ho* in steel ma(ing gained over fourdecades$ S%I&'s #onsultancy Division S%I

S%I& has a *elle,uipped Research and Development #entre for Iron and Steel RD#IS! atRanchi$ *hich helps to produce ,uality steel and develop ne* technologies for the steelindustry. -esides$ S%I& has its o*n inhouse #entre for 3ngineering and Technology #3T!$0anagement Training Institute 0TI! and Safety 6rganisation at Ranchi. 6ur captive minesare under the control of the Ra* 0aterials Division in #alcutta. The 3nvironment0anagement Division and =ro*th Division of S%I& operate from their head,uarters in#alcutta. %lmost all our plants and ma1or units are IS6 #ertified.

0a1or >nits of S%I&

Integrated Steel Plants at -hilai Steel Plant -SP! in #hhattisgarh$ Durgapur Steel

Plant DSP! in ;est -engal$ Rour(ela Steel Plant RSP! in 6rissa and -o(aro Steel

Plant -S&! in har(hand

Special Steel Plants at %lloy Steels Plants %SP! in ;est -engal$ Salem Steel Plant

SSP! in Tamil


3/113


1.2 n O!er!ie" of #$% Centre for &ron and 'teel (#%C&')* '&+

The Research Development #entre for Iron Steel RD#IS! at Ranchi is the corporate R D unit of S%I&. Set up in AB:C$ the #entre has IS65 BA certification to its credit. Itunderta(es R D pro1ect in diverse realms of Iron Steel Technology under the categoriesof -asic Scientific Research$ Plant Performance Improvement$ Investigation #onsultancy%ssignments$ 3,uipments Instrument Design and 0a1or Technology Development.

RD#IS has more than 7 dedicated and competent scientists and engineers and its

laboratory is e,uipped *ith around 7 sophisticated diagnostic research e,uipment and Epilot plant facilities.

RD#IS provides customers *ith prompt$ innovative and costeffective R D solutions+develop and commerciali/e improved processes and products+ continually enhance thecapability of its human resources to emerge as a center of e)cellence. The ma1or efforts aredirected to*ards cost reduction$ ,uality improvement and valueaddition to products of S%I&plants and providing application engineering support to S%I&4s products at customers end.RD#IS$ along *ith steel plants$ has recently ta(en initiatives to develop special steelproducts utili/ing the moderni/ed production facilities at steel plants.

RD#IS also offers technological services to various organi/ations in the form of5 @no* F ho*transfer of technologies developed by RD#IS+ #onsultancy services+ Speciali/ed testingservices+ #ontrast research and technology a*areness programmes.



4/113


5/113


DSP has al*ays attached ma)imum importance on proper training and development of itsemployees. Its #entre for Human Resource Development has all modern facilities includingthe stateoftheart 3lectrical and 3lectronics laboratory$ Hydraulics and Pneumaticslaboratory and *or(shop for effective training and development of its employees.

&ocation5

Situated at a distance of AE8 (m from #alcutta$ its geographical location is defined as C7C:'


6/113


2.2. Background of the ProectBackground of the Proect

Research Development #entre for Iron Steel RD#IS! at Ranchi developed an

information system "Human Resource Information System HRIS!$ for Durgapur SteelPlant DSP!. HRIS is an information system that4s an aid for managing the human resourceat the Durgapur Steel Plant. 6n completion of the soft*are development$ the DurgapurSteel Plant sho*ed an interest in computerising of areas such as employees' leave record$safety related functions and management of gate pass and statutory re,uirements at#ontract &abour #ell #!. The re,uired system$ basically$ deals *ith areas not consideredin HRIS.

So$ the ne* re,uired system is more of an e)tension to a "Human Resource InformationSystem HRIS!". %s the HRIS pro1ect *as underta(en by the RD#IS$ so the additionaldemand to develop the e)tension to the already developed system is ta(en in hand by theRD#IS only. This ne* pro1ect is much more than 1ust the continuous soft*are support fromRD#IS for implementation of developed modules. So$ the RD#IS proposed a ne* soft*aredevelopment pro1ect for "#omputeri/ation of leave records$ contract labour cell and safetydepartment at DSP."



7/113


3.3. uman #esource &nformation 'ystemuman #esource &nformation 'ystem

3.1 he Purpose of #&'

% HRIS is implemented of Durgapur Steel Plant DSP!. HRIS stands for Human ResourceInformation System. The Human Resource Information System HRIS! is a record system. Itis the central repository for personnel and payroll data. HRIS supplies information andstatistics on all employees. The data provided is used to determine ho* human resourcesare being managed.

HRIS reports data on all employees to *hom the DSP pays or reimburses salaries orbenefits$ regardless of funding sources or reporting system+ maintains data on former andcurrent employees+ and stores historical personnel data for in,uiry and analysis.

3.2 he &mpact of &mplementing an #&'

Integrated HR Information Systems HRIS! have a profound effect on firms that implementthem. 0ost often these firms are replacing several related systems$ such as a personneldatabase$ payroll system and benefits system$ *ith one single HRIS that does it all. 0anypeople focus on the improved reporting and processing that *ill be reali/ed from the ne*system$ and those are the reasons most firms choose to implement a ne* HRIS. -ut *hatmany people don4t focus on is that the ne* HRIS *ill most li(ely affect the company muchmore deeply F it *ill challenge the operating structure and principles of all the HRrelateddepartments.

%ctually$ in an organi/ation$ the pressure is on for proactive HR innovations that contributedirectly to the bottomline or improve employee morale and efficiency. %1u*on CC! pointsout that the typical HR professional gets involved *ith one step in many different flo*s of*or(. ?ery often the involvement of HR has no purpose e)cept to validate the process in

some *ay and acts as an interruption to the flo* of *or(. In other *ords$ the HR function isa 'gate(eeper for information that4s been deemed too highly classified for the data o*ner.'So$ HR is not actually ma(ing a measurable contribution in fact$ the opposite. HRinvolvement creates a ,ueue or delay in the process. ;e should as($ if the HR involvementis really necessary.

6nce upon a time the HR database had an 'allornothing' ,uality probably because it *aspaperbased. -ut no* technology allo*s controlled access to various portions of thedatabase. So an employee can safely amend his or her o*n address or ban( accountdetails$ *hile the ability to change certain appraisal details might be confined to the linemanager. In either case$ there is no reason for HR to be involved. HR should move on fromthe role of intermediary. The 1ob that used to create delay in an organi/ation$ is handled

pretty comfortably by the computeri/ed Human Resource Information System.So$ it can be said that an integrated HRIS results is a drastically different environment than acluster of related but separate systems. The core concept of a centrali/ed data storeinherent *ith an HRIS demands integrated *or( processes for consistently managing thatstore. The t*o attributes F centrali/ed data storage and integrated *or( processes F *illaffect the company in *ays most managers don4t e)pect.


8/113


providing *ide access to corporate videos$ training$ etc. 6bviously$ email announcementsand ne*sletters can also be used to alert employees to ne* developments or urgentre,uests.



9/113


3.3 Planning and setting up a ne" uman resource information system (#&') 4anagement of # 'ystems

There are three primary activities in an HRIS implementation F

configuring the HRIS for the firm4s business processes and policies$

interfacing data *ith other systems and converting historical data into the HRIS$

preparing the organi/ation for the ne* HRIS.

Implementing a ne* HR information system HRIS! is one pro1ect$ *hich re,uires a goodpro1ect plan F to serve as a road map. Implementing a full HRIS$ or health and safety$re,uires sufficient time to be spent to plan out the future course of action.

% good planning can be possible by follo*ing the guidelines.

3.5 %e!eloping the plan

The pro1ect leader's initial tas( is to develop the plan. The more comple) the system$ themore detail the plan needs. The ,uestions to ans*er are5

;hat has to be done

In *hat order should tas(s be completed

;ho i going to do it

-y *hat deadline and



10/113


;hat is the impact of one tas( on the others

-rea(ing the *or( do*n into tas(s that can be assigned to individuals is vital to pro1ectplanning. 3ach main tas( can have numbered subtas(s to assist in trac(ing.

%nother approach is to dra* a chart that identifies the time line as *ell as (ey pro1ect due

dates. The pro1ect plan is to be monitored periodically to report the progress. Basic raining. 2or proper development and implementation of the system$ some

training on the system is re,uired. Training is often delivered in a onetime dose of t*o tofour days$ covering in rapid succession everything that4s needed to (no* about thesystem. %n overvie* of the system navigation$ functions$ file structure andcustomi/ation features is important before moving further on the pro1ect.

6inding 7ays to &mpro!e 7ork 6lo". Technology provides a *onderful opportunity to

e)amine the *or( flo* in the HR department$ to as( some hard ,uestions about oldpolicies and procedures$ and to as( *hy and ho* the department does *hat it does.%long the *ay$ (no*ing ho* technology can support changes in operations i vital. Thene* system has the capability to change the *or(flo*. In streamlining compensation$

for e)ample$ it could be proposed that the line manager have direct access toperformance information and merit increases. #an the system give the manager accessto this information *hile at the same time guarding the data files %nother e)ample5Since the applicanttrac(ing program can produce labels$ *ill the printer handlepostcards so that the process of addressing and affi)ing labels can be eliminated


11/113


accurate$ then there isn4t any need to go for data conversion. %s$ the time and troubleta(en to define file layouts$ test them and do the conversion may not be feasible.

o


12/113


o =athering current reports and determining the value of each.

o Revie*ing the vendor's standard reports and printing out samples using your

employee database.

o Intervie*ing managers to find out *hat information they need and in *hat

format.o =etting report*riting training from the vendor.

o Testing (ey reports.

o Printing formats and sample reports for your recordsmanagement manual.

'ystem dministration5 #omputer systems do not ta(e care of themselves+ someone

must be responsible and accountable for each application in the department. Theimplementation plan should determine *ho *ill be using the system and *hat type ofprivileges each person *ill have. Privileges refers to the type of access to activities$ fromvie*ing data to entering data to maintaining the code tables. There are three primarytas(s in planning for system administration5

o 2irst$ clarification of the relationships bet*een payroll and HR for access and

system maintenance.

o Then assignment of responsibilities for bac(up$ archiving$ installing

enhancements and training ne* users.

o Third$ coordination of the system administration tas(s *ith the systems

department$ decide *ho in HR *ill be the system administrator and plan forthat person's training.

Communication of Changes5 ;hat difference *ill the ne* system ma(e to the

organi/ation outside of HR There *ill be several different audiences for the

communications e)ecutives$ line managers and other employees. The most fre,uentmista(e is to either not plan at all for the communications or to announce the system'sbenefits too soon and set up e)pectations long before they can be met. Steps in thecommunication plan are to

o Identify the impact of the system on different groups.

o Define any information or participation that may be needed such as verifying

data or responding to a survey.

o &et people (no* ho* the *or( is progressing through an employee ne*sletter

or other publication.

o Describe of the changes and benefits after they are implemented$ giving

specific e)amples.

6n implementation of the plan$ its monitoring is done *ith the time line. This *ill sho* ho*the system is developed efficiently *ee( by *ee($ tas( by tas(.



13/113


5.5. 'oft"are %e!elopment +ife Cycle ('%+C)'oft"are %e!elopment +ife Cycle ('%+C)

The System Development &ife #ycle is the process of developing information systemsthrough investigation$ analysis$ design$ implementation$ and maintenance. The SystemDevelopment &ife #ycle SD! is also (no*n as Information Systems Development or

%pplication Development.

System Development &ife #ycle involves a number of steps. 3ach phase *ithin the overallcycle may be made up of several steps.



14/113

Feasibility Study

S/W Requirement Specification

Software Design

Software Development

Testing

ser Training

Implementation

Documentation


pproach

2easibility Study

Soft*are Re,uirement Specification

o Database Design

o >ser Interface 2orm! Design

o Report Design

Soft*are Development

o Database Tables F #reating 0aster Tables

o >ser Interfaces F 2orm development

o Reports

Testing

>ser Training

Implementation

Documentation



15/113


8.8. 6easi9ility 'tudy6easi9ility 'tudy

8.1 6easi9ility 'tudy

The main ob1ective of feasibility study activity is to determine *hether it *ould be feasible todevelop the product. The feasibility study activity involves the analysis of the problem andcollection of all relevant information relation to the product such different data items *hich*ould be input to the system.

8.2 # 'ahyak 6easi9ility 'tudy:

8.2.1 9stract pro9lem definition:

The ob1ective is to develop a system that facilitates computeri/ation for online and effectivecontrol of safety functions$ compensation and leave records of the employee at DurgapurSteel Plant DSP!$ Durgapur.

This system is an e)tension to a "Human Resource Information System HRIS!" developedby RD#IS$ S%I& for Durgapur Steel Plant.

The system$ basically$ deals *ith areas not considered in HRIS$ such as$ employees+ safetyrelated functions$ leave record and management of gate pass and statutory re,uirements of#ontract &abour #ell #!.

8.2.2 6ormulation of the different solution strategies

The re,uired ob1ective F of a system that facilitates computeri/ation for online and effectivecontrol of safety functions$ compensation and leave records of the employee at DurgapurSteel Plant DSP!$ Durgapur can be achieved by

1ust providing the e)tension to the previous Information System by ma(ing the additions

to the already developed systeminuse at Durgapur Steel Plant DSP!.

forming a ne* pro1ect that *or(s *ith the previous one$ sharing the re,uired information.

The additional demand is accomplished *ith a ne* soft*are development pro1ect for"#omputeri/ation of leave records$ contract labour cell and safety department at DSP".

8.2.3 nalysis of alternati!e solution strategies

The ne* re,uired system is more of an e)tension to a "Human Resource InformationSystem HRIS!". %s the HRIS pro1ect *as underta(en by the RD#IS$ so the additionaldemand to develop the e)tension to the already developed system is ta(en in hand by the

RD#IS only. This ne* pro1ect is much more than 1ust the continuous soft*are support fromRD#IS for implementation of developed modules. So$ the RD#IS proposed a ne* soft*aredevelopment pro1ect for "#omputeri/ation of leave records$ contract labour cell and safetydepartment at DSP".



16/113


;.;. 'oft"are #e


17/113


;.2 6unctional #e


18/113


;.2.2 6unctional #e


19/113


3& 3arn &eave

2& 2estival &eave

36& 3)tra 6rdinary &eave

HP& Half Pay &eave

S%-& Sabbatical &eave

#60& #ommuted &eave

TR& Transit &eave

0%T& 0aternity &eave

K& Kuarantine &eave

S#& Special #asual &eave

SD& Special Disability &eave

S& Study &eave

&


20/113


21/113


compensation amount on receipt of order from personneldepartment.

#ompensation amount to be paid to the employee is

computed based on the guidelines from #ompensation %ct$ABC7. It includes the factor based on age$ minimum amount

to be paid as per %ct and percentage of loss of permanentearning capacity.

Input5

6utput5

Processing5


Safety Functions

!eave Compensation

3fficient0anpo*er>tili/ation

%ccident detail0aintenance

&eave Records0anagement


22/113


;.2.5 # 'ahayak: 'ystem Concept for 'afety 6unction and Compensation



23/113


;.2.8 # 'ahayak: 'ystem Concept for 'afety 6unction and Compensation



24/113


25/113


;.3 0onfunctional #e


26/113


3nsure that minor defects in the application or component are easy to correct.

3nsure that minor enhancements to the application or component are relatively easy

to implement.

0inimi/e maintenance costs.

0inimi/e maintenance organi/ation staffing needs e.g.$ to free up maintenance

programmers for ne* development!.

Different types of maintainability re,uirements for The system5

#orrectability Re,uirements corrective maintenance!$ *hich is restricted to fi)ing

defects *hile system is in use.

o It is concerned *ith the ease to *hich minor defects can be corrected

bet*een ma1or releases of the system i.e.$ *hile the thing *ith defects is inuse!.

o 3nsure that minor defects in the application or component can be easily and,uic(ly5

Identified$

>nderstood$ and

#orrected.

o 0inimi/e defect correction costs.

3)tensibility Re,uirements adaptive maintenance!$ *hich is restricted to minor

enhancements of the application.

o It is concerned *ith the degree to *hich system can be enhanced in the

future to meet changing re,uirements or goals.

o The system should be developed in such a *ay that it enables architects and

designers to partially base their choices on foreseen enhancements.

o The design should ensure that future enhancements to an application or

component can be easily and ,uic(ly to implemented.

o 0inimi/e enhancement costs.

It should be e)tendible. The application is made to parse HT0& te)t documents tocreate the &e)icon. It should be designed in such a *ay that the parsing to L0&documents etc. can be possible 1ust by attaching an additional module for e)tractingle)icon data from a particular format.

To provide ease to maintain The system and components the application should provide5

0odular soft*are

Information hiding implementation

;elldefined interfaces

6b1ectorientation and componentbased development.



27/113


28/113


>.>. 'oft"are %esign'oft"are %esign

>.1 %ata9ase %esign

Database design is the process of producing a detailed data model of a database. Thismodel contains all the needed physical design choices and physical storage parametersneeded to generate DD& *hich can then be used to create a database. % fully attributed datamodel contains detailed attributes for each entity.

>.1.1 ntityrelationship modelThe 3ntityRelationship model is a data model for highlevel descriptions of conceptual datamodels$ and it provides a graphical notation for representing such data models in the form ofentityrelationship diagrams. Such data models are typically used in the first stage ofinformationsystem design+ they are used$ for e)ample$ to describe information needs andJorthe type of information that is to be stored in the database during the re,uirements analysis.The modelling techni,ue$ ho*ever$ can be used to describe any ontology i.e. an overvie*and classification of used terms and their relationships! for a certain universe of discoursei.e. area of interest!. In the case of the design of an information system that is based on adatabase$ the conceptual data model is$ at a later stage usually called logical design!$mapped to a logical data model$ such as the relational model+ this in turn is mapped to aphysical model during physical design. Sometimes$ both of these phases are referred to as"physical design".



29/113


>.1.2 #eduction of an # 'chema to a9les

% database that is represented as an 3R database schema can be represented as acollection of tables. 2or each entity set and for each relationship set in the database$ thereis a uni,ue table.

-oth 3R model and the relationaldatabase model are abstract$ logical representations ofreal*orld enterprises. -ecause t*o models employ similar design principles$ it is possibleto convert an 3R design into a relational design.

The set of Tables turned out to be5

%ccidentMDet

#ompensation

&eave

&eaveMDet

&eaveM3ncash

&eaveM&imit

#ompM%ct

%ccident

#ompM3arnM&ossMTable

&ocation

0achine

&eaveMIntMHoliday

#ompM2actor

PerM#ategory

%ccM#ategory

-odyMPart

&eaveMType

Ignorant

In1uryMnsafeM#ondition

>nsafeM%ct

3,uipment



30/113


>.1.3 a9les &nternals


ACCIDENT_IDSLNONAMEAGESHIFTALIVEADDR1ADDR2ADDR3CITYSTATEUNFIT_FROMUNFIT_TOMEDICAL_COSTWAGE_COSTINDIRECT_COSTMAN_HR_LOSTPLNODEPT_CODESUB_DEPT_CODEWORK_AREA_CODEGRADE_CODEDESG_CODEDSG_SUFFIXINJ_NATURE_CODEBODY_PART_CODEPER_CAT_CODEACC_CAT_CODEUNSAFE_ACT_CODEIGNORANT_CODEREMARK

ACCIDENT_IDSLNONAMEAGESHIFTALIVEADDR1ADDR2AD

DR3CITYSTATEUNFIT_FROMUNFIT_TOMEDICAL_COSTWAGE_COSTINDIRECT_COSTMAN_HR_LOSTPLNODEPT_CODESUB_DEPT_CODEWORK_AREA_CODEGRADE_CODEDESG_CODEDSG_SUFFIXINJ_NATURE_CODEBODY_PART_CODEPER_CAT_CODEACC_CAT_CODEUNSAFE_ACT_CODEIGNORANT_CODEREMARK


31/113



ACCIDENT_IDACCIDENT_DET_SLNOAPPLLICATION_DATEPLNOAGEFACTORAVG_SALARYEARN_LOSSDSCRORD_NOORD_DATECOMP_AMOUNTWAGE_UPPER_LIMITCOMP_ACT_VALID_FROMCOMP_ELT_VALID_FROMCOMP_ELT_SLNOCOMP_FACT_VALID_FROMFATAL

_PCTFATAL_LOW_AMOUNTNON_FATAL_PCTNON_FATAL_LOW_AMOUNT


32/113


33/113



PLNOTYPE_CODELEAVE_DATE_FROMSLNODATE_FROMDATE_TOBASIC_LEAVE_CODENO_OF_DAYSENTERY_ONFLAGACCIDENT_IDACCIDENT_SLNOFIN_XFR_DATEFIN_XFR_STATUS

PLNOBASIC_LEAVE_CODESLNOENCASH_MTH_YRNO_OF_DAYSAMOUNTENTRY_ONFLAGSTATUSFIN_XFR_DATEFIN_XFR_STATUS


34/113



BASIC_LEAVE_CODELEAVE_RULE_CODEVALID_FROMVALID_TONO_OF_DAYSREQ_PR_DAYS_YRBONUS_DAYS_YRDAYS_LIMIT_YR

VALID_FROMVALID_TOFATAL_PCTFATAL_LOWNON_FATAL_PCTNON_FATAL_LOW_AMOUNTWAGE_UPPER_LIMITACT_DSCR


35/113



IDINCIDENT_DATEDSCRLOCATION_CODECAUSE_CODEUNSAFE_CON_CODESAFETY_ACTION

SLNOVALID_FROMVALID_TODSCREARN_LOSS_PCTDISPLAY_SLNO

CODEDSCRDEPT_CODESUB_DEPT_CODEWORK_AREA_CODE


36/113



ACCIDENT_IDSLNOEQUIPTMENT_CODEMC_HR_LOSTREMARKS

PLNOLEAVE_TYPE_CODELEAVE_DATE_FROMHOLIDAY_DATEOFF_HOLIDAY

AGEVALID_FROMVALID_TOFACTOR


37/113



CODEDSCRPER_CAT_TYPE

CODEDSCRAC_CATEGORY_TYPE

CODEDSCRBODY_PART

CODEDSCRNO_OF_DAYS


38/113



CODEDSCR CODEDSCR

CODEDSCR CODEDSCR

CODEDSCR CODEDSCR

CODEDSCR CODEDSCREQUIP_TYPE


39/113


>.1.5 4odule "ise a9le ssociation

0odule *ise the functions carried out at DSP is mentioned earlier$ *hile studying functionalre,uirements. Here for each module function *ise associated table is sho*n. %lso table *isefield level detail is enclosed. This gives the complete idea about the information that *ill be

captured in the developed system for any function.

'afety 4odule

The person from Safety 3ngineering Department *ill be responsible for operating functionsunder this module. Safety department *ill enter the data for accident and unfit durationI6;! in case of employee4s accident. -uilding of uptodate full employee database ismandatory for implementation of this module. 2unction *ise associated tables are5

S.S3

7. >nsafe #ondition >


40/113



ACCIDENT_IDSLNONAMEAGES

HIFTALIVEADDR1ADDR2ADDR3

CITYSTATEUNFIT_FROMUNFIT

_TOMEDICAL_COSTWAGE_COST

INDIRECT_COSTMAN_HR_LOST

PLNODEPT_CODESUB_DEPT

_CODEWORK_AREA_CODEGRA

DE_CODEDESG_CODEDSG_SUF

FIXINJ_NATURE_CODEBODY

_PART_CODEPER_CAT_CODEACC_CAT_CODEUNSAFE_ACT_

CODEIGNORANT_CODEREMARK


41/113


Compensation 4odule

#ompensation payment includes five agencies as mentioned above. Ho*ever the developedsoft*are *ill have interaction *ith Safety 3ngineering Department Personnel Department.The medical board could not be thought of due to nonavailability of net*or( connectivity.6ther departments *ere discarded$ as implementation is difficult *hen too many persons

are involved for the operation.

Personnel department *ill operate this module centrally. The data created *ill be lin(ed *ithaccident information. The prere,uisite for implementation of this module is availability of

>ptodate full employee database

>ptodate accident information

The soft*are *ill compute the compensation amount to be paid based on the logic given byDSP. -ut one can change this amount manually if re,uired. The formula used forcompensation amount is given belo*5

#ompensation %mountO #ompensation 2actor L Percentage of permanentearning capacity loss L Percentage to be paid 2atal J


42/113


43/113


The computeri/ed leave record system *ill not only provide easy access of availableinformation at #IT but *ill help personnel department to ta(e out the leave orders. Thepersonnel officer *ill operate this module. The soft*are *ill validate the leave related dataentry based on employee *ise balanced leave account in Payroll System at #IT. Thismodule *ill have online access of leave and attendance data of payroll system. Thesoft*are under this module *ill deal *ith

&eave Rule

&eave limitation as per leave rule

3ntry ?alidation of &eave Record &eave #onsumption!

Display of balance leave account

Display of attendance data

Printing of various leave order

The module *ill not have interface for employees4 attendance and *ill e)clude the soft*are

for leave accumulation and leave accounting. These functions are already operational at#IT department as mentioned earlier. The functional e)isting system *ill be coupled *iththis module.

RD#IS discussed *ith #IT and personnel department regarding the access of leave andattendance data in Payroll System. It *as agreed upon that #IT *ould provide read onlydata access in the follo*ing structure5

Sl


44/113


A. &eave Rule &3%?3MR>&3

C. -asic &eave Type -%SI#M&3%?3MTNP3

7. &eave Type &3%?3MTNP3

9. &eave limitation as per Rule &3%?3M&I0IT

E. %ttendance J &eave from Pay -ills %TTM0%ST3RMP-

Transaction 0odules

A. &eave availedJconsumed &3%?3

C. DetailsJcomposition of leave &3%?3MD3T

7. Intervening Holidays &3%?3MI


45/113


>.2 ,ser &nterface (6orm) %esign

%ccording to The Dictionary of #omputing4$ >ser Interface Design refers to the aspects ofhard*are or soft*are *hich can be seen or heard or other*ise perceived! by the humanuser$ and the commands and mechanisms the user uses to control its operation and input

data.

;hile >ser Interface Design is often used for computer systems$ it is the part of any systeme)posed to a user. In a computer system$ the user typically interacts *ith an operatingsystem or *ith application soft*are such as a spreadsheet or a *ord processor. ;ithsystems$ the user interacts using menus$ icons$ (eystro(es$ mouse clic(s$ and similarcapabilities.

In this pro1ect$ a set of CA possible >sercomputer interaction points are identified. So$ thepossible set of >ser Interfaces can be5

%ccident Detail

3mployee4s &eave 3ncashment

Safety 0aster

o %ccident #ategory

o -ody Parts

o #ause

o 3,uipment

o Ignorant

o In1ury nsafe %ct

o >nsafe #ondition

&eave &imitation


46/113


>.2.1 ,ser &nterface %esign: ccident %etail

"ccident Detail

Incidence

ID Date &oc Department SDp

%rea

#ause >nsafe#on

Detail Safe %ct

"ccident Detail

S.


47/113


>.2.2 ,ser &nterface %esign: mployee?s +ea!e ncashment

#mployee$s !eave #ncas%ment

Pl


48/113


>.2.3 ,ser &nterface %esign: 'afety 4aster ccident Category

Safety &aster

%## -ody #ause 3,uip Ignore In1ury &oc Per %ct #ond.

"ccident Category

#ode Description %cc #at Type



49/113


>.2.5 ,ser &nterface %esign: 'afety 4aster Body Parts

Safety &aster


'ody (arts

#ode Description -ody Part



50/113


>.2.8 ,ser &nterface %esign: 'afety 4aster Cause

Safety &aster


Cause

#ode Description



51/113


>.2.; ,ser &nterface %esign: 'afety 4aster


52/113


>.2.> ,ser &nterface %esign: 'afety 4aster &gnorant

Safety &aster


Ignorant

#ode Description



53/113


>.2.@ ,ser &nterface %esign: 'afety 4aster &nury 0ature

Safety &aster


In)ury *ature

#ode Description



54/113


55/113


>.2.1 ,ser &nterface %esign: 'afety 4aster Person Category

Safety &aster


(erson Category

#ode Description Per #at. Type



56/113


>.2.11 ,ser &nterface %esign: 'afety 4aster ,nsafe ct

Safety &aster


nsafe "ct

#ode Description



57/113


>.2.12 ,ser &nterface %esign: 'afety 4aster ,nsafe Condition

Safety &aster


nsafe Condition

#ode Description



58/113


>.2.13 ,ser &nterface %esign: +ea!e +imitation (0o. of %ays)

!eave !imitation +*o, of

Days-

&eave#ode

&eave Rule ?alidity 0a) &eave%ccum Days!

Re,Pr

DaysJNr

-onusDaysJ

Nr

0a)&eave

#ode Dscr 2rom To %ccumJNr



59/113


>.2.15 ,ser &nterface %esign: ++C Block ears

!!TC 'loc. ears

-loc( Standard



60/113


>.2.18 ,ser &nterface %esign: Basic +ea!e ype

'asic !eave Type

#ode Description



61/113


>.2.1; ,ser &nterface %esign: +ea!e ype

!eave Type

#ode Description Permitted 0a) Days



62/113


>.2.1> ,ser &nterface %esign: #elation

Relation

#ode



63/113


>.2.1@ ,ser &nterface %esign: +ea!e #ules

!eave Rules

#ode Description



64/113


>.2.1A ,ser &nterface %esign: 7orkmenDs Compensation 6actor

Wor.men$s Compensation Factor

?alid from Date ?alid to Date %ge Nears #ompensation 2actor



65/113


>.2.2 ,& %esign: &nuries #esulting in Permanent +oss of arning Capacity

In)uries Resulting in (ermanent !oss of #arning Capacity

SI


66/113


>.2.21 ,ser &nterface %esign: 7orkmenDs Compensation ct %etail

Wor.men$s Compensation "ct Detail

?alid2rom

?alid To2atal %ccident


67/113


@.@. 'oft"are %e!elopment'oft"are %e!elopment

In consultation *ith concerned person from DSP$ RD#IS *ould carry out the applicationsoft*are development follo*ing the standard approach of SS%D System %nalysis %ndDesign!. The soft*are developed *ill be open in nature allo*ing dynamic additions andmodifications of standardi/ation module by the users themselves. The hard coding *ill beavoided and *herever re,uired a loo(up table *ill be provided for easy data entry. RD#IS*ould handover the 3RD 3ntity Relation Diagram! and entire source code to DSP oncompletion of the pro1ect. The soft*are *ill be developed for clientserver environmenthaving 6racle Bi as bac( end database on >


68/113


@.2 ard"are $ 'ystem 'oft"are

The hard*are and associated soft*are items other than the application soft*are *ill beprovided by DSP. The installation of hard*are$ system soft*are including 6racle RD-0S$frontend oracle tools Developer Gi! *ill be done by DSP. Similarly responsibility of net*or(design$ net*or( components procurement and their installation *ill lie *ith DSP. RD#IS *ill

be responsible for installation of application soft*are at the client machine and ma(ing itoperational at node.



69/113


A.A. CodingCoding

A.1 'E+ Code

CODES FOR MASTER TABLE STANDARDISATIONCREATE TABLE ACC_CATEGORY !CODE VARCHAR2!3" NOT NULL#DSCR VARCHAR2!$%" NOT NULL#ACC_CAT_TYPE VARCHAR2!1" NOT NULL"

CREATE TABLE BODY_PART !CODE VARCHAR2!3" NOT NULL#DSCR VARCHAR2!$%" NOT NULL#BODY_PART VARCHAR2!1" NOT NULL"

CREATE TABLE CAUSE !CODE VARCHAR2!3" NOT NULL#DSCR VARCHAR2!$%" NOT NULL"

CREATE TABLE EQUIPMENT !CODE VARCHAR2!3" NOT NULL#DSCR VARCHAR2!$%" NOT NULL#EQUIP_TYPE VARCHAR2!1" NOT NULL"

CREATE TABLE IGNORANT !CODE VARCHAR2!3" NOT NULL#DSCR VARCHAR2!$%" NOT NULL"

CREATE TABLE INJURY_NATURE !CODE VARCHAR2!3" NOT NULL#DSCR VARCHAR2!$%" NOT NULL"

CREATE TABLE LOCATION !CODE VARCHAR2!$" NOT NULL#DSCR VARCHAR2!$%" NOT NULL#DEPT_CODE NUMBER!&" NOT NULL#SUB_DEPT_CODE NUMBER!3" NOT NULL#WORK_AREA_CODE VARCHAR2!1%" NOT NULL"

CREATE TABLE PER_CATEGORY !CODE VARCHAR2!3" NOT NULL#DSCR VARCHAR2!$%" NOT NULL#PER_CAT_TYPE VARCHAR2!1" NOT NULL"

CREATE TABLE UNSAFE_CONDITION !CODE VARCHAR2!3" NOT NULL#DSCR VARCHAR2!$%" NOT NULL"

CREATE TABLE UNSAFE_ACT !CODE VARCHAR2!3" NOT NULL#DSCR VARCHAR2!$%" NOT NULL"



70/113


CREATE TABLE ACCIDENT !ID NUMBER!'" NOT NULL#INCIDENT_DATE DATE NOT NULL#DSCR VARCHAR2!$%%" NOT NULL#LOCATION_CODE VARCHAR2!$" NOT NULL#CAUSE_CODE VARCHAR2!3" NOT NULL#UNSAFE_CON_CODE VARCHAR2!3" NOT NULL#SAFETY_ACTION VARCHAR2!2%%""

CREATE TABLE ACCIDENT_DET !ACCIDENT_ID NUMBER!'" NOT NULL#SLNO NUMBER!3" NOT NULL#NAME VARCHAR2!$%" NOT NULL#AGE NUMBER!3" NOT NULL#SHIFT VARCHAR2!1" NOT NULL#ALIVE VARCHAR2!1" NOT NULL#ADDR1 VARCHAR2!$%"#ADDR2 VARCHAR2!$%"#ADDR3 VARCHAR2!$%"#CITY VARCHAR2!2%"#STATE VARCHAR2!2%"#UNFIT_FROM DATE#UNFIT_TO DATE#MEDICAL_COST NUMBER!1"#WAGE_COST NUMBER!1"#

INDIRECT_COST NUMBER!1"#MAN_HR_LOST NUMBER!$"#PLNO NUMBER!'"#DEPT_CODE NUMBER!&"#SUB_DEPT_CODE NUMBER!3"#WORK_AREA_CODE VARCHAR2!1%"#GRADE_CODE VARCHAR2!$"#DESG_CODE VARCHAR2!1%"#DESG_SUFFIX VARCHAR2!1%"#INJ_NATURE_CODE VARCHAR2!3" NOT NULL#BODY_PART_CODE VARCHAR2!3" NOT NULL#PER_CAT_CODE VARCHAR2!3" NOT NULL#ACC_CAT_CODE VARCHAR2!3" NOT NULL#UNSAFE_ACT_CODE VARCHAR2!3" NOT NULL#IGNORANT_CODE VARCHAR2!3" NOT NULL#REMARKS VARCHAR2!1%%""

CREATE TABLE MACHINE_DET !ACCIDENT_ID NUMBER!'" NOT NULL#SLNO NUMBER!3" NOT NULL#EQUIPMENT_CODE VARCHAR2!3" NOT NULL#MC_HR_LOST NUMBER!$#1" NOT NULL#REMARKS VARCHAR2!1%%""

CREATE TABLE COMP_ACT !VALID_FROM DATE NOT NULL#VALID_TO DATE#FATAL_PCT NUMBER!$#2" NOT NULL#FATAL_LOW_AMOUNT NUMBER!1" NOT NULL#NON_FATAL_PCT NUMBER!$#2" NOT NULL#NON_FATAL_LOW_AMOUNT NUMBER!1" NOT NULL#WAGE_UPPER_LIMIT NUMBER!1" NOT NULL#ACT_DSCR VARCHAR2!3%%""

CREATE TABLE COMP_EARN_LOSS_TABLE !VALID_FROM DATE NOT NULL#

VALID_TO DATE#SLNO VARCHAR2!(" NOT NULL#DSCR VARCHAR2!1%%" NOT NULL#EARN_LOSS_PCT NUMBER!$#2" NOT NULL#DISPLAY_SLNO NUMBER!'" NOT NULL"

CREATE TABLE COMP_FACTOR !VALID_FROM DATE NOT NULL#VALID_TO DATE#AGE NUMBER!" NOT NULL#FACTOR NUMBER!(#3" NOT NULL"

CREATE TABLE COMPENSATION !ACCIDENT_ID NUMBER!'" NOT NULL#ACCIDENT_DET_SLNO NUMBER!3" NOT NULL#APPLICATION_DATE DATE NOT NULL#PLNO NUMBER!'" NOT NULL#AGE NUMBER!" NOT NULL#

FACTOR NUMBER!(#3" NOT NULL#AVG_SALARY NUMBER!1" NOT NULL#EARN_LOSS_PCT NUMBER!$#2" NOT NULL#



71/113


72/113


AMOUNT NUMBER!1" NOT NULL#ENTRY_ON DATE NOT NULL#FLAG VARCHAR2!1" NOT NULL#STATUS VARCHAR2!1"#FIN_XFR_DATE DATE#FIN_XFR_STATUS VARCHAR2!1""

ALTER TABLE ACC_CATEGORY

ADD CONSTRAINT ACC_CAT_PK PRIMARY KEY !CODE"ALTER TABLE BODY_PARTADD CONSTRAINT BODY_PART_PK PRIMARY KEY !CODE"ALTER TABLE CAUSEADD CONSTRAINT CAUSE_PK PRIMARY KEY !CODE"ALTER TABLE EQUIPMENTADD CONSTRAINT EQUIPMENT_PK PRIMARY KEY !CODE"ALTER TABLE IGNORANTADD CONSTRAINT IGNORANT_PK PRIMARY KEY !CODE"ALTER TABLE INJURY_NATUREADD CONSTRAINT INJ_NATURE_PK PRIMARY KEY !CODE"ALTER TABLE LOCATIONADD CONSTRAINT LOCATION_PK PRIMARY KEY !CODE"ALTER TABLE LOCATIONADD CONSTRAINT LOCATION_WORK_AREA_FK FOREIGN KEY !DEPT_CODE# SUB_DEPT_CODE# WORK_AREA_CODE"REFERENCES WORK_AREA !DEPT_CODE# SUB_DEPT_CODE# CODE"

ALTER TABLE PER_CATEGORYADD CONSTRAINT PER_CAT_PK PRIMARY KEY !CODE"ALTER TABLE UNSAFE_ACTADD CONSTRAINT UNSAFE_ACT_PK PRIMARY KEY !CODE"ALTER TABLE UNSAFE_CONDITIONADD CONSTRAINT UNSAFE_CON_PK PRIMARY KEY !CODE"ALTER TABLE ACCIDENTADD CONSTRAINT ACCIDENT_PK PRIMARY KEY !ID"ALTER TABLE ACCIDENTADD CONSTRAINT ACCIDENT_LOCATION_FK FOREIGN KEY !LOCATION_CODE" REFERENCES LOCATION !CODE"ADD CONSTRAINT ACCIDENT_CAUSE_FK FOREIGN KEY !CAUSE_CODE" REFERENCES CAUSE !CODE"ADD CONSTRAINT ACCIDENT_UNSAFE_CON_FK FOREIGN KEY !UNSAFE_CON_CODE" REFERENCESUNSAFE_CONDITION !CODE"ALTER TABLE ACCIDENT_DETADD CONSTRAINT ACIDENTDET_PK PRIMARY KEY !ACCIDENT_ID# SLNO"ALTER TABLE ACCIDENT_DETADD CONSTRAINT ACIDENTDET_ACC_CAT_FK FOREIGN KEY !ACC_CAT_CODE" REFERENCES ACC_CATEGORY!CODE"ADD CONSTRAINT ACIDENTDET_UNSAFE_ACT_FK FOREIGN KEY !UNSAFE_ACT_CODE" REFERENCES UNSAFE_ACT!CODE"ADD CONSTRAINT ACIDENTDET_IGNORANT_FK FOREIGN KEY !IGNORANT_CODE" REFERENCES IGNORANT !CODE"ADD CONSTRAINT ACIDENTDET_ACCIDENT_FK FOREIGN KEY !ACCIDENT_ID" REFERENCES ACCIDENT !ID"ADD CONSTRAINT ACIDENTDET_EMPLOYEE_FK FOREIGN KEY !PLNO" REFERENCES EMPLOYEE !PLNO"ADD CONSTRAINT ACIDENTDET_WORK_AREA_FK FOREIGN KEY !DEPT_CODE# SUB_DEPT_CODE# WORK_AREA_CODE"REFERENCES WORK_AREA !DEPT_CODE# SUB_DEPT_CODE# CODE"ADD CONSTRAINT ACIDENTDET_GRADE_FK FOREIGN KEY !GRADE_CODE" REFERENCES GRADE !CODE"ADD CONSTRAINT ACIDENTDET_DESG_FK FOREIGN KEY !DESG_CODE" REFERENCES DESG !CODE"ADD CONSTRAINT ACIDENTDET_INJ_NATURE_FK FOREIGN KEY !INJ_NATURE_CODE" REFERENCESINJURY_NATURE !CODE"ADD CONSTRAINT ACIDENTDET_BODY_PART_FK FOREIGN KEY !BODY_PART_CODE" REFERENCES BODY_PART!CODE"ADD CONSTRAINT ACIDENTDET_PER_CAT_FK FOREIGN KEY !PER_CAT_CODE" REFERENCES PER_CATEGORY!CODE"

ALTER TABLE MACHINE_DETADD CONSTRAINT MACHINEDET_PK PRIMARY KEY !ACCIDENT_ID# SLNO"ALTER TABLE MACHINE_DETADD CONSTRAINT MACHINEDET_ACCIDENT_FK FOREIGN KEY !ACCIDENT_ID" REFERENCES ACCIDENT !ID"ADD CONSTRAINT MACHINEDET_EQUIPMENT_FK FOREIGN KEY !EQUIPMENT_CODE" REFERENCES EQUIPMENT!CODE"ALTER TABLE LEAVE_RULEADD CONSTRAINT LEAVE_RULE_PK PRIMARY KEY !CODE"ALTER TABLE LEAVE_RULEADD CONSTRAINT LEAVE_RULE_UK UNIQUE !DSCR"ALTER TABLE BASIC_LEAVE_TYPEADD CONSTRAINT BASIC_LEAV_PK PRIMARY KEY !CODE"ALTER TABLE LEAVE_TYPEADD CONSTRAINT LEAVE_TYPE_PK PRIMARY KEY !CODE"ALTER TABLE LEAVE_LIMITADD CONSTRAINT LEAVE_LMT_PK PRIMARY KEY !BASIC_LEAVE_CODE# LEAVE_RULE_CODE# VALID_FROM"

ALTER TABLE LEAVE_LIMITADD CONSTRAINT LEAVE_LMT_LEAVE_RULE_FK FOREIGN KEY !LEAVE_RULE_CODE" REFERENCES LEAVE_RULE!CODE"



73/113


ADD CONSTRAINT LEAVE_LMT_BASIC_LEAV_FK FOREIGN KEY !BASIC_LEAVE_CODE" REFERENCESBASIC_LEAVE_TYPE !CODE"ALTER TABLE LEAVEADD CONSTRAINT LEAVE_PK PRIMARY KEY !PLNO# LEAVE_TYPE_CODE# DATE_FROM"ALTER TABLE LEAVEADD CONSTRAINT LEAVE_LEAVE_TYPE_FK FOREIGN KEY !LEAVE_TYPE_CODE" REFERENCES LEAVE_TYPE !CODE"ADD CONSTRAINT LEAVE_EMPLOYEE_FK FOREIGN KEY !PLNO" REFERENCES EMPLOYEE !PLNO"ALTER TABLE LEAVE_DET

ADD CONSTRAINT LEAVE_DET_PK PRIMARY KEY !PLNO# TYPE_CODE# LEAVE_DATE_FROM# SLNO"ALTER TABLE LEAVE_DETADD CONSTRAINT LEAVE_DET_ACIDENTDET_FK FOREIGN KEY !ACCIDENT_ID# ACCIDENT_SLNO" REFERENCESACCIDENT_DET !ACCIDENT_ID# SLNO"ADD CONSTRAINT LEAVE_DET_LEAVE_FK FOREIGN KEY !PLNO# TYPE_CODE# LEAVE_DATE_FROM" REFERENCESLEAVE !PLNO# LEAVE_TYPE_CODE# DATE_FROM"ADD CONSTRAINT LEAVE_DET_BASIC_LEAV_FK FOREIGN KEY !BASIC_LEAVE_CODE" REFERENCESBASIC_LEAVE_TYPE !CODE"ALTER TABLE LEAVE_INT_HOLIDAY ADD CONSTRAINT LEAVEHOLI_PK PRIMARY KEY !PLNO# LEAVE_TYPE_CODE# LEAVE_DATE_FROM#HOLIDAY_DATE"ALTER TABLE LEAVE_INT_HOLIDAYADD CONSTRAINT LEAVEHOLI_LEAVE_FK FOREIGN KEY !PLNO# LEAVE_TYPE_CODE# LEAVE_DATE_FROM"REFERENCES LEAVE !PLNO# LEAVE_TYPE_CODE# DATE_FROM"ALTER TABLE LEAVE_ENCASHADD CONSTRAINT LEAVE_CASH_PK PRIMARY KEY !PLNO# BASIC_LEAVE_CODE# SLNO"

ALTER TABLE LEAVE_ENCASHADD CONSTRAINT LEAVE_CASH_BASIC_LEAV_FK FOREIGN KEY !BASIC_LEAVE_CODE" REFERENCESBASIC_LEAVE_TYPE !CODE"ADD CONSTRAINT LEAVE_CASH_EMPLOYEE_FK FOREIGN KEY !PLNO" REFERENCES EMPLOYEE !PLNO"ALTER TABLE COMP_ACTADD CONSTRAINT COMP_ACT_PK PRIMARY KEY !VALID_FROM"ALTER TABLE COMP_FACTORADD CONSTRAINT COMP_FACT_PK PRIMARY KEY !VALID_FROM# AGE"ALTER TABLE COMP_EARN_LOSS_TABLEADD CONSTRAINT COMP_ELT_PK PRIMARY KEY !VALID_FROM# SLNO"ALTER TABLE COMPENSATIONADD CONSTRAINT COMP_PK PRIMARY KEY !ACCIDENT_DET_SLNO# ACCIDENT_ID"ALTER TABLE COMPENSATIONADD CONSTRAINT COMP_ACIDENTDET_FK FOREIGN KEY !ACCIDENT_ID# ACCIDENT_DET_SLNO" REFERENCESACCIDENT_DET !ACCIDENT_ID# SLNO"ADD CONSTRAINTCOMP_EMPLOYEE_FK FOREIGN KEY !PLNO" REFERENCES EMPLOYEE !PLNO"ADD CONSTRAINT COMP_COMP_ACT_FK FOREIGN KEY !COMP_ACT_VALID_FROM" REFERENCES COMP_ACT!VALID_FROM"ADD CONSTRAINT COMP_COMP_ELT_FK FOREIGN KEY !COMP_ELT_SLNO# COMP_ELT_VALID_FROM" REFERENCESCOMP_EARN_LOSS_TABLE !SLNO# VALID_FROM"ADD CONSTRAINT

COMP_COMP_FACT_FK FOREIGN KEY !COMP_FACT_VALID_FROM# AGE" REFERENCES COMP_FACTOR!VALID_FROM# AGE"

CREATE INDEX LOCATION_WORK_AREA_FK_I ON LOCATION !DEPT_CODE# SUB_DEPT_CODE# WORK_AREA_CODE"CREATE INDEX ACCIDENT_CAUSE_FK_I ON ACCIDENT !CAUSE_CODE"CREATE INDEX ACCIDENT_LOCATION_FK_I ON ACCIDENT !LOCATION_CODE"CREATE INDEX ACCIDENT_UNSAFE_CON_FK_I ON ACCIDENT !UNSAFE_CON_CODE"CREATE INDEX ACIDENTDET_ACC_CAT_FK_I ON ACCIDENT_DET !ACC_CAT_CODE"CREATE INDEX ACIDENTDET_BODY_PART_FK_I ON ACCIDENT_DET !BODY_PART_CODE"CREATE INDEX ACIDENTDET_IGNORANT_FK_I ON ACCIDENT_DET !IGNORANT_CODE"CREATE INDEX ACIDENTDET_INJ_NATURE_FK_I ON ACCIDENT_DET !INJ_NATURE_CODE"

CREATE INDEX ACCIDENTDET_WORK_AREA_FK_I ON ACCIDENT_DET !DEPT_CODE# SUB_DEPT_CODE#WORK_AREA_CODE"CREATE INDEX ACIDENTDET_PER_CAT_FK_I ON ACCIDENT_DET !PER_CAT_CODE"CREATE INDEX ACIDENTDET_UNSAFE_ACT_FK_I ON ACCIDENT_DET !UNSAFE_ACT_CODE"CREATE INDEX ACIDENTDET_ACCIDENT_FK_I ON ACCIDENT_DET !ACCIDENT_ID"CREATE INDEX ACIDENTDET_DESG_FK_I ON ACCIDENT_DET !DESG_CODE"CREATE INDEX ACIDENTDET_EMPLOYEE_FK_I ON ACCIDENT_DET !PLNO"CREATE INDEX ACIDENTDET_GRADE_FK_I ON ACCIDENT_DET !GRADE_CODE"CREATE INDEX MACHINEDET_ACCIDENT_FK_I ON MACHINE_DET !ACCIDENT_ID"CREATE INDEX MACHINEDET_EQUIPMENT_FK_I ON MACHINE_DET !EQUIPMENT_CODE"CREATE INDEX COMP_COMP_ACT_FK_I ON COMPENSATION !COMP_ACT_VALID_FROM"CREATE INDEX COMP_COMP_ELT_FK_I ON COMPENSATION !COMP_ELT_VALID_FROM# COMP_ELT_SLNO"CREATE INDEX COMP_COMP_FACT_FK_I ON COMPENSATION !COMP_FACT_VALID_FROM# AGE"CREATE INDEX COMP_ACIDENTDET_FK_I ON COMPENSATION !ACCIDENT_ID# ACCIDENT_DET_SLNO"CREATE INDEX COMP_EMPLOYEE_FK_I ON COMPENSATION !PLNO"CREATE INDEX LEAVE_LMT_BASIC_LEAV_FK_I ON LEAVE_LIMIT !BASIC_LEAVE_CODE"

CREATE INDEX LEAVE_LMT_LEAVE_RULE_FK_I ON LEAVE_LIMIT !LEAVE_RULE_CODE"CREATE INDEX LEAVE_LEAVE_TYPE_FK_I ON LEAVE !LEAVE_TYPE_CODE"CREATE INDEX LEAVE_EMPLOYEE_FK_I ON LEAVE !PLNO"



74/113


CREATE INDEX LEAVE_DET_ACCIDENTDET_FK_I ON LEAVE_DET !ACCIDENT_ID# ACCIDENT_SLNO"CREATE INDEX LEAVE_DET_LEAVE_FK_I ON LEAVE_DET !PLNO# TYPE_CODE# LEAVE_DATE_FROM"CREATE INDEX LEAVE_DET_BASIC_LEAV_FK_I ON LEAVE_DET !BASIC_LEAVE_CODE"CREATE INDEX LEAVEHOLI_LEAVE_FK_I ON LEAVE_INT_HOLIDAY !PLNO# LEAVE_TYPE_CODE#LEAVE_DATE_FROM"CREATE INDEX LEAVE_CASH_BASIC_LEAV_FK_I ON LEAVE_ENCASH !BASIC_LEAVE_CODE"CREATE INDEX LEAVE_CASH_EMPLOYEE_FK_I ON LEAVE_ENCASH !PLNO"

A.2 P+ 'E+ Code

T*+,,-*!FORM COMP_FACTOR"WHEN_NEW.FORM_INSTANCE

DECLARE/_,*0-_*o4- VARCHAR2!$"5

67_+ Fo*7Mo84-59:_+ B4o;:59:_07- VARCHAR2!&%"5

BEGINS-_W+o!FORMS_MDI_WINDOW# WINDOW_STATE# MAXIMI?E"5

S-_W+o!FORMS_MDI_WINDOW# TITLE# @Co7=8-*+- H870 R-o8*;- I6o*70+oS>-7@"5

S-_W+o!@WINDOW1@# WINDOW_STATE# MAXIMI?E"5 IF USER @HRIS@ THEN BEGIN SELECT ,*0-_*o4- INTO /_,*0-_*o4- FROM *+_8-* WHERE 8-*_+ USER5 IF /_,*0-_*o4- NOT IN !@ADMIN@" THEN

67_+ F+_Fo*7!S>-7C8**-_Fo*7"59:_07- G-_Fo*7_P*o=-*>!67_+# FIRST_BLOCK"5

WHILE 9:_07- IS NOT NULL LOOP9:_+ F+_B4o;:!9:_07-"5

SET_BLOCK_PROPERTY!9:_+# INSERT_ALLOWED# PROPERTY_FALSE"5 SET_BLOCK_PROPERTY!9:_+# DELETE_ALLOWED# PROPERTY_FALSE"5 SET_BLOCK_PROPERTY!9:_+# UPDATE_ALLOWED# PROPERTY_FALSE"5

SET_BLOCK_PROPERTY!9:_+# QUERY_ALLOWED# PROPERTY_TRUE"5 9:_07- G-_B4o;:_P*o=-*>!9:_+# NEXTBLOCK"5

END LOOP5END IF5

EXCEPTION WHEN NO_DATA_FOUND THEN =*o;_7,!@ERROR O*0;4- ID + o VALID HRIS 8-*@"5 RAISE FORM_TRIGGER_FAILURE5 END5

END IF5END5

2WHEM_WINDOW_RESI?ED

DECLARE /_0- VARCHAR2!$%"5BEGIN /_0- GET_WINDOW_PROPERTY!FORMS_MDI_WINDOW# WINDOW_STATE"5 IF /_0- IN !@NORMAL@# @MINIMI?E@" THEN SET_WINDOW_PROPERTY!FORMS_MDI_WINDOW# WINDOW_STATE# MAXIMI?E"5 END IF5END53KEY_ENTQRY

CLEAR_RECORD5ENTER_QUERY5

&KEY_EXEQRYIF SYSTEMMODE @ENTER.QUERY@ THEN CLEAR_RECORD5 EXECUTE_QUERY5

ELSE EXECUTE_QUERY5END IF5



75/113


76/113


;0*!1"59-,+

o=- =*+70*>_;8*56-; =*+70*>_;8* +o /_=*+70*>_877>5+6 =*+70*>_;8*6o8 -

=*o;_7,!@ERROR O/-*40==+, P-*+o C-;: V04+ F*o7 0 V04+ To D0-@"5 ;4o- =*+70*>_;8*5

*0+- 6o*7_*+,,-*_60+48*-5- +65;4o- =*+70*>_;8*5

-5&PRE.UPDATE

-;40*-;8*o* =*+70*>_;8* + -4-; @@

6*o7 ;o7=_60;o* _877> ;0*!1"5

9-,+o=- =*+70*>_;8*5

6-; =*+70*>_;8* +o /_=*+70*>_877>5 +6 =*+70*>_;8*6o8 - =*o;_7,!@ERROR F+44 8= - V04+ To D0- 6o* o4 *-;o*@"5 ;4o- =*+70*>_;8*5 *0+- 6o*7_*+,,-*_60+48*-5 - +65 ;4o- =*+70*>_;8*5-5

-;40*-;8*o* =*+70*>_;8* + -4-; @@ 6*o7 ;o7=_60;o* ;0*!1"59-,+

o=- =*+70*>_;8*56-; =*+70*>_;8* +o /_=*+70*>_877>5

+6 =*+70*>_;8*6o8 -=*o;_7,!@ERROR O/-*40==+, P-*+o C-;: V04+ F*o7 0 V04+ To D0-@"5

;4o- =*+70*>_;8*5*0+- 6o*7_*+,,-*_60+48*-5

- +65;4o- =*+70*>_;8*5

-5

3ITEMVALIDFROMTRIGGERWHEN.VALIDATE.ITEM

..

.. B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%% -;+o

..

+6 o! COMP_FACTORVALID_FROM IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5



77/113


- +65.... E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%% -;+o..

&AGETRIGGERWHEN.VALIDATE.ITEM

..

.. B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%1 -;+o

..+6 o! COMP_FACTORAGE IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5- +65.... E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%1 -;+o..$FACTORTRIGEERWHEN.VALIDATE.ITEM

.. B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%2 -;+o

..

+6 o! COMP_FACTORFACTOR IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5- +65.... E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%2 -;+o..

FORMCOMP_EARN_LOSS_TABLETRIGGERWHEN.NEW.FORM.INSTANCE


67_+ Fo*7Mo84-59:_+ B4o;:59:_07- VARCHAR2!&%"5


S-_W+o!FORMS_MDI_WINDOW# TITLE# @Co7=8-*+- H870 R-o8*;- I6o*70+oS>-7@"5 S-_W+o!@WINDOW1@# WINDOW_STATE# MAXIMI?E"5 IF USER @HRIS@ THEN BEGIN SELECT ,*0-_*o4- INTO /_,*0-_*o4- FROM *+_8-* WHERE 8-*_+ USER5 IF /_,*0-_*o4- NOT IN !@ADMIN@" THEN



SET_BLOCK_PROPERTY!9:_+# INSERT_ALLOWED# PROPERTY_FALSE"5 SET_BLOCK_PROPERTY!9:_+# DELETE_ALLOWED# PROPERTY_FALSE"5 SET_BLOCK_PROPERTY!9:_+# UPDATE_ALLOWED# PROPERTY_FALSE"5 SET_BLOCK_PROPERTY!9:_+# QUERY_ALLOWED# PROPERTY_TRUE"5 9:_07- G-_B4o;:_P*o=-*>!9:_+# NEXTBLOCK"5

END LOOP5END IF5

EXCEPTION WHEN NO_DATA_FOUND THEN =*o;_7,!@ERROR O*0;4- ID + o VALID HRIS 8-*@"5 RAISE FORM_TRIGGER_FAILURE5 END5

END IF5END5



78/113


2WHEN.WINDOERESI?ED

DECLARE /_0- VARCHAR2!$%"5BEGIN /_0- GET_WINDOW_PROPERTY!FORMS_MDI_WINDOW# WINDOW_STATE"5 IF /_0- IN !@NORMAL@# @MINIMI?E@" THEN

SET_WINDOW_PROPERTY!FORMS_MDI_WINDOW# WINDOW_STATE# MAXIMI?E"5 END IF5END5

3KEY.ENTQRY

CLEAR_RECORD5ENTER_QUERY5&KEY.EXEQRY

IF SYSTEMMODE @ENTER.QUERY@ THEN CLEAR_RECORD5 EXECUTE_QUERY5ELSE EXECUTE_QUERY5

END IF5$ON.MESSAGE

=*o;_7,!MESSAGE_TEXT @ !@ MESSAGE_TYPE @.@ TO_CHAR!MESSAGE_CODE" @"@"5$ON.ERROR=*o;_7,!ERROR_TEXT @ !@ ERROR_TYPE @.@ TO_CHAR!ERROR_CODE" @"@"5DATABLOCKCOMP_EARNLOSS_TABLRTRIGGER1KEY.DELREC.... B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ COMP_ELT_PK -;+o..-;40*- ;8*o* =*+70*>_;8* + -4-; @@ 6*o7 HRISCOMPENSATION _877> ;0*!1"59-,+ +6 ! ! COMP_EARN_LOSS_TABLEVALID_FROM + o 844 " 0 ! COMP_EARN_LOSS_TABLESLNO +o 844 " " - o=- =*+70*>_;8*5 6-; =*+70*>_;8* +o =*+70*>_877>5 +6 ! =*+70*>_;8*6o8 " - =*o;_7,!@ERROR C0o -4-- D-0+4 *-;o* -+ + COMPENSATION T094-@"5 ;4o- =*+70*>_;8*5 *0+- 6o*7_*+,,-*_60+48*-5 - +65 ;4o- =*+70*>_;8*5 - +65-5

-4--_*-;o*5.... E -6084 -6o*;- 00 +-,*+> ;o*0+ COMP_ELT_PK -;+o..2WHEN.VALIDATE.RECORD

+6 !>-7*-;o*_08 @QUERY@" -+6 !;o7=_-0*_4o_094-/04+_o + o 844 0

;o7=_-0*_4o_094-/04+_6*o7 ;o7=_-0*_4o_094-/04+_o" - =*o;_7,!@ERROR V04+ F*o7 D0- o84 9- -0*4+-* 0 V04+ To@"5 *0+- 6o*7_*+,,-*_60+48*-5- +65

- +653PRE.INSERT-;40*-

;8*o* =*+70*>_;8* +

-4-; @@ 6*o7 ;o7=_-0*_4o_094-


79/113


/_=*+70*>_877> ;0*!1"59-,+

o=- =*+70*>_;8*56-; =*+70*>_;8* +o /_=*+70*>_877>5+6 =*+70*>_;8*6o8 -

=*o;_7,!@ERROR F+44 V04+ To D0- o6 =*-/+o8 E0*+, Lo T094-@"5 ;4o- =*+70*>_;8*5

*0+- 6o*7_*+,,-*_60+48*-5

- +65;4o- =*+70*>_;8*5

-5

-;40*-;8*o* =*+70*>_;8* + -4-; @@ 6*o7 ;o7=_-0*_4o_094- _;8*56-; =*+70*>_;8* +o /_=*+70*>_877>5+6 =*+70*>_;8*6o8 -


*0+- 6o*7_*+,,-*_60+48*-5- +65;4o- =*+70*>_;8*5

-5&PRE.UPDATE-;40*-

;8*o* =*+70*>_;8* + -4-; @@ 6*o7 ;o7=_-0*_4o_094- _877> ;0*!1"59-,+

o=- =*+70*>_;8*56-; =*+70*>_;8* +o /_=*+70*>_877>5+6 =*+70*>_;8*6o8 -

=*o;_7,!@ERROR F+44 V04+ To D0- o6 =*-/+o8 E0*+, Lo T094-@"5 ;4o- =*+70*>_;8*5

*0+- 6o*7_*+,,-*_60+48*-5- +65;4o- =*+70*>_;8*5

-5-;40*-

;8*o* =*+70*>_;8* + -4-; @@ 6*o7 ;o7=_-0*_4o_094- ;0*!1"59-,+

o=- =*+70*>_;8*56-; =*+70*>_;8* +o /_=*+70*>_877>5+6 =*+70*>_;8*6o8 -


*0+- 6o*7_*+,,-*_60+48*-5- +65

;4o- =*+70*>_;8*5-5ITEM



80/113


TRIGEER1SLNOWHEN.VALIDATE.ITEM.. B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()1% -;+o..+6 o! COMP_EARN_LOSS_TABLESLNO IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5

*0+- 6o*7_*+,,-*_60+48*-5- +65.... E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()1% -;+o..2DSCRWHEN.VALIDATE.ITEM... B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()11 -;+o..+6 o! COMP_EARN_LOSS_TABLEDSCR IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5- +65.... E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()11 -;+o

..3EARN.LOSS.PCTWHEN.VALIDATE.ITEM.... B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()12 -;+o..+6 o! COMP_EARN_LOSS_TABLEEARN_LOSS_PCT IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5- +65.... E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()12 -;+o..&DISPLAI.SLNOWHEN.VALIDATE.ITEM.. B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()13 -;+o..+6 o! COMP_EARN_LOSS_TABLEDISPLAY_SLNO IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5- +65.... E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()13 -;+o..$VALID.FROMWHEN.VALIDATE.ITEM.. B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()% -;+o..+6 o! COMP_EARN_LOSS_TABLEVALID_FROM IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5- +65..

.. E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()% -;+o

..

COMP_ACT _FMBFORMCOMP_ACTTRIGGERWHEN.NEW.FORM.INSTANCE


67_+ Fo*7Mo84-59:_+ B4o;:59:_07- VARCHAR2!&%"5




81/113


S-_W+o!FORMS_MDI_WINDOW# TITLE# @Co7=8-*+- H870 R-o8*;- I6o*70+oS>-7@"5 S-_W+o!@WINDOW1@# WINDOW_STATE# MAXIMI?E"5 IF USER @HRIS@ THEN BEGIN SELECT ,*0-_*o4- INTO /_,*0-_*o4-

FROM *+_8-* WHERE 8-*_+ USER5 IF /_,*0-_*o4- NOT IN !@ADMIN@" THEN



SET_BLOCK_PROPERTY!9:_+# INSERT_ALLOWED# PROPERTY_FALSE"5 SET_BLOCK_PROPERTY!9:_+# DELETE_ALLOWED# PROPERTY_FALSE"5 SET_BLOCK_PROPERTY!9:_+# UPDATE_ALLOWED# PROPERTY_FALSE"5 SET_BLOCK_PROPERTY!9:_+# QUERY_ALLOWED# PROPERTY_TRUE"5 9:_07- G-_B4o;:_P*o=-*>!9:_+# NEXTBLOCK"5

END LOOP5END IF5

EXCEPTION WHEN NO_DATA_FOUND THEN

=*o;_7,!@ERROR O*0;4- ID + o VALID HRIS 8-*@"5 RAISE FORM_TRIGGER_FAILURE5 END5

END IF5END52WHEN.WINDOW.RESI?EDDECLARE /_0- VARCHAR2!$%"5BEGIN /_0- GET_WINDOW_PROPERTY!FORMS_MDI_WINDOW# WINDOW_STATE"5 IF /_0- IN !@NORMAL@# @MINIMI?E@" THEN SET_WINDOW_PROPERTY!FORMS_MDI_WINDOW# WINDOW_STATE# MAXIMI?E"5 END IF5END53KEY.ENTQRYCLEAR_RECORD5ENTER_QUERY5&KEY.EXEQRY

IF SYSTEMMODE @ENTER.QUERY@ THEN CLEAR_RECORD5 EXECUTE_QUERY5ELSE EXECUTE_QUERY5END IF5$ON.MESSAGE=*o;_7,!MESSAGE_TEXT @ !@ MESSAGE_TYPE @.@ TO_CHAR!MESSAGE_CODE" @"@"5'%N_ERROR=*o;_7,!ERROR_TEXT @ !@ ERROR_TYPE @.@ TO_CHAR!ERROR_CODE" @"@"5DATABLOCK

COMP_ACTTRIGEER1KEY_DELREC

..

.. B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ COMP_ACT_PK -;+o

..-;40*- ;8*o* =*+70*>_;8* + -4-; @@ 6*o7 HRISCOMPENSATION _877> ;0*!1"59-,+ +6 ! ! COMP_ACTVALID_FROM + o 844 " " - o=- =*+70*>_;8*5 6-; =*+70*>_;8* +o =*+70*>_877>5 +6 ! =*+70*>_;8*6o8 " -

=*o;_7,!@ERROR C0o -4-- D-0+4 *-;o* -+ + COMPENSATION T094-@"5 ;4o- =*+70*>_;8*5 *0+- 6o*7_*+,,-*_60+48*-5



82/113


- +65 ;4o- =*+70*>_;8*5 - +65-5-4--_*-;o*5.... E -6084 -6o*;- 00 +-,*+> ;o*0+ COMP_ACT_PK -;+o..

2WHEN.VALIDATE.RECORD+6 !>-7*-;o*_08 @QUERY@" -

+6 !;o7=_0;/04+_o + o 844 0 ;o7=_0;/04+_6*o7 ;o7=_0;/04+_o" -

=*o;_7,!@ERROR V04+ F*o7 D0- o84 9- -0*4+-* 0 V04+ To@"5 *0+- 6o*7_*+,,-*_60+48*-5- +65

- +653PRE.INSERT-;40*-

;8*o* =*+70*>_;8* + -4-; @@ 6*o7 ;o7=_0; _877> ;0*!1"5

9-,+o=- =*+70*>_;8*56-; =*+70*>_;8* +o /_=*+70*>_877>5+6 =*+70*>_;8*6o8 -

=*o;_7,!@ERROR F+44 V04+ To D0- o6 =*-/+o8 A;@"5 ;4o- =*+70*>_;8*5

*0+- 6o*7_*+,,-*_60+48*-5- +65;4o- =*+70*>_;8*5

-5

-;40*-;8*o* =*+70*>_;8* + -4-; @@ 6*o7 ;o7=_0; _;8*56-; =*+70*>_;8* +o /_=*+70*>_877>5+6 =*+70*>_;8*6o8 -


*0+- 6o*7_*+,,-*_60+48*-5- +65;4o- =*+70*>_;8*5

-53PRE.UPDATE

-;40*-;8*o* =*+70*>_;8* + -4-; @@ 6*o7 ;o7=_0; _877> ;0*!1"59-,+

o=- =*+70*>_;8*56-; =*+70*>_;8* +o /_=*+70*>_877>5+6 =*+70*>_;8*6o8 -

=*o;_7,!@ERROR F+44 V04+ To D0- o6 =*-/+o8 A;@"5 ;4o- =*+70*>_;8*5

*0+- 6o*7_*+,,-*_60+48*-5- +65

;4o- =*+70*>_;8*5-5-;40*-



83/113


;8*o* =*+70*>_;8* + -4-; @@ 6*o7 ;o7=_0; ;0*!1"59-,+

o=- =*+70*>_;8*56-; =*+70*>_;8* +o /_=*+70*>_877>5+6 =*+70*>_;8*6o8 -


*0+- 6o*7_*+,,-*_60+48*-5- +65;4o- =*+70*>_;8*5

-5

ITEM

1VALID_FROMTRIGGERWHEN_VALIDATE_ITEM.... B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%3 -;+o..+6 o! COMP_ACTVALID_FROM IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5- +65.... E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%3 -;+o..2FATAL_PCTWHEN_VALIDATE_ITEM.... B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%& -;+o..+6 o! COMP_ACTFATAL_PCT IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5- +65.... E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%& -;+o..3FATAL_LOE_AMOUNTWHEN_VALIDATE_ITEM.... B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%$ -;+o..+6 o! COMP_ACTFATAL_LOW_AMOUNT IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5

- +65.... E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%$ -;+o..&NON_FATAL_PCTWHEN_VALIDATE_ITEM.... B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%' -;+o..+6 o! COMP_ACTNON_FATAL_PCT IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5- +65.... E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%' -;+o..

$NON_FATAL_LOW_AMOUNTWHEN_VALIDATE_ITEM



84/113


.. B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%( -;+o

..+6 o! COMP_ACTNON_FATAL_LOW_AMOUNT IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5- +65..

.. E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%( -;+o

..'WAGE_UPPER_LIMITWHEN_VALIDATE_ITEM

.. B-,+ -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%) -;+o

..+6 o! COMP_ACTWAGE_UPPER_LIMIT IS NOT NULL " - 7-0,-! @WHEN.VALIDATE.ITEM *+,,-* 60+4- o 6+-4 . @ >-7*+,,-*_6+-4 "5 *0+- 6o*7_*+,,-*_60+48*-5- +65.... E -6084 -6o*;- 00 +-,*+> ;o*0+ SYS_C%%$()%) -;+o..



85/113


86/113


87/113


1.3 7hite 9oF testing

;hite bo) testing$ clear bo) or structural testing is used in computer programming$ soft*areengineering and soft*are testing to chec( that the outputs of a program$ given certain inputs$conform to the internal design and implementation of the program.

The term *hite bo) indicates that the tester closely e)amines the internal implementation ofthe program being tested. % complementary techni,ue$ blac( bo) testing or functionaltesting$ chec(s that the program performs to its specification *ithout e)amining its internalimplementation.

1.5 Code co!erage

#ode coverage is a measure used in soft*are testing. It describes the degree to *hich thesource code of a program has been tested. It is distinct from blac( bo) testing methodsbecause it loo(s at the code directly$ rather than other measures such as soft*are functionsor ob1ect interfaces.

#ode coverage techni,ues *ere amongst the first techni,ues invented for systematic

soft*are testing. There are a number of different *ays of measuring code coverage$ themain ones being5

Statement #overage Has each line of the source code been e)ecuted and tested

#ondition #overage Has each evaluation point such as a trueJfalse decision! been

e)ecuted and tested

Path #overage Has every possible route through a given part of the code been

e)ecuted and tested

Some of the coverage criteria above are connected+ for instance$ path coverage implies bothcondition and statement coverage. Statement coverage does not imply condition coverage$

as the code in the # programming language! belo* sho*s5void fooint bar!

printf"this is"!+

if bar A!

printf"not "!+

U

printf"a positive integer"!+return+

U

If the function "foo" *as called *ith variable "bar A"$ statement coverage *ould beachieved. #ondition coverage$ ho*ever$ *ould not.

2ull path coverage$ of the type described above$ is usually impractical or impossible. %nymodule *ith a succession of n decisions in it can have up to Cn paths *ithin it+ loopconstructs can result in an infinite number of paths. 0any paths may also be infeasible$ inthat there is no input to the program under test that can cause that particular path to bee)ecuted. Ho*ever$ there is no generalpurpose algorithm for identifying infeasible paths

because such an algorithm could be used to solve the halting problem!. Techni,ues forpractical path coverage testing instead attempt to identify classes of code paths that differ



88/113


only in the number of loop e)ecutions$ and to achieve "basis path" coverage the tester mustcover all the path classes.

>sually the source code is instrumented and run through a series of tests. The resultingoutput is then analysed to see *hat areas of code have not been e)ercised$ and the testsare updated to include these areas as necessary. #ombined *ith other code coverage

methods the aim is to develop a rigorous yet manageable set of regression tests.

#ode coverage is ultimately e)pressed as a percentage$ as in ";e have tested G:Q of thecode". The meaning of this depends on *hat forms! of code coverage have been used$ asG:Q path coverage is more comprehensive than G:Q statement coverage.

1.8 'oft"are testing acti!ities

1.8.1 ,nit test

In computer programming$ a unit test is a method of testing the correctness of a particularmodule of source code.

The idea is to *rite test cases for every nontrivial function or method in the module so thateach test case is separate from the others if possible.

-enefits

The goal of unit testing is to isolate each part of the program and sho* that the individualparts are correct. It provides a *ritten contract that the piece must satisfy. This isolatedtesting provides t*o main benefits5

3ncourages change

>nit testing allo*s the programmer to refactor code at a later date$ and ma(e sure themodule still *or(s correctly regression testing!. This provides the benefit of encouraging

programmers to ma(e changes to the code since it is easy for the programmer to chec( ifthe piece is still *or(ing properly.

Simplifies Integration

>nit testing helps eliminate uncertainty in the pieces themselves and can be used in abottomup testing style approach. -y testing the parts of a program first and then testing thesum of its parts *ill ma(e integration testing easier.

&imitations

It is important to reali/e that unittesting *ill not catch every error in the program. -ydefinition$ it only tests the functionality of the units themselves. Therefore$ it *ill not catchintegration errors$ performance problems and any other system*ide issues. >nit testing is

only effective if it is used in con1unction *ith other soft*are testing activities.

%pplications

The unit testing concept is part of the 3)treme Programming method of soft*areengineering. >nit testing is the building bloc( to test driven development TDD!. 3)tremeProgramming and most other methods use unit tests to perform blac( bo) testing.

This is also (no*n as "programmer tests".

1.8.2 &ntegration testing

Integration testing is the phase of soft*are testing in *hich individual soft*are modules arecombined and tested as a group. It follo*s unit testing and precedes system testing.



89/113


90/113


11.11. ppendiFppendiF

11.1ppendiF G : ,ser &nterface (6orms) for # 'ahyak

The >ser Interface for HR SahVya( application is$ more of$ a specification for the loo( andfeel of the program. The user issues commands via the >I to computer applications. 2or theease of the user of the HR SahVya($ >I is developed for providing an interface to theapplication. The >I of the HR SahVya( receive information from and display information to auser.

The >ser Interface for HR SahVya( is a type of computerhuman interface on a computer. %ta conceptual level$ a computerhuman interface is a "means by *hich people and computerscommunicate *ith each other". The interface F HR SahVya( 's >I directly binds the user tothe operation and functionality of the program. % good >I design removes the impediment ofcommunication *ith the program and allo*s the user to *or( directly on the problem athand.



91/113


11.1.1 # 'ahyak 6orm =1:



92/113


11.1.2 # 'ahyak 6orm =2:



93/113


11.1.3 # 'ahyak 6orm =3a:



94/113


11.1.5 # 'ahyak 6orm =39:



95/113


11.1.8 # 'ahyak 6orm =3c:



96/113


11.1.; # 'ahyak 6orm =3d:



97/113


11.1.> # 'ahyak 6orm =3e:



98/113


11.1.@ # 'ahyak 6orm =3f:



99/113


11.1.A # 'ahyak 6orm =3g:



100/113


11.1.1 # 'ahyak 6orm =3h:



101/113


11.1.11 # 'ahyak 6orm =3i:



102/113


11.1.12 # 'ahyak 6orm =3:



103/113


11.1.13 # 'ahyak 6orm =5:



104/113


11.1.15 # 'ahyak 6orm =8:



105/113


11.1.18 # 'ahyak 6orm =;:



106/113


11.1.1; # 'ahyak 6orm =>:

http://studen

hr information project report[www.students3k.com]

Documents