wasa project

8/12/2019 WASA Project

1/127

Human Resource Management System Of WASA

College Of Computer Science and Information Studies, GCUF 1

CHAPTER-1

Project Introduction

1.1IntroductionThis chapter introduces the desktop based application for WASA (Water and Sanitation

Agency) Human Resource Management System. The main functionality of this project is related

to develop best computerized system for WASA employees.

1.2 Business RequirementsThe requirements that are found by the studying the problem domain and having a couple of

sessions with the user (employee) are as follows:

1. The system is required a computerized way for management of employees record.2. This system is required a secure database i.e. any record once entered will never be delete

or modify by any user/data entry operator .Only managing person can change any detail

of specific record.

3. Employee record is the core requirement of this software.4. This system is required the online access to the database server from anywhere in the

office.

5. This system is also required the complete representation of analyzed information throughreports.

1.2.1 backgroundCurrently in WASA they are saving there employee record manually which is causing following

problems:

1. Time consuming2. Manual file management3. Inefficient updating4. Less secure5. Chance of error6. Labor cost7. Chance of data loss8. Complexity9. Stationary & other overheads10.High cost11.More Human effort


2/127



12.Difficult to find a single record out of 1000s13. Human error might be occurs14.Retrieval of data is very slow

1.2.2 Business OpportunityDue to our newly developed system, management problem is solved which was major

issue for administration. This project offer for users to get right information with no

error and within seconds which was not possible in the manual system.

1.2.3Business Objectives and SuccessCriteriaDesigning any computerized system is important and helpful to establish the business

objectives of the new system.

Our new system is flexible and capable of adapting to changing environmentalconditions. Thus this system is designed so to meet its desired objectives and

institutional goals. It is acceptable to the organizational design standards and provides a smooth

flow of information from one step to the next.

Accuracy has been increased during data storage and report generation. The new system is error free and efficient in searching. It provides proper data storage and maintenance. There is no need of

maintaining huge amount of files and registers to handle valuable data.

All type of timely reports is generated which facilitate the management to setthe dimensions about expenditure in a right way.

The update & Previous old record of every employee is also provided in asystem.

The report of every employee easily generated. It is not time consuming, it is time saving i.e. a single record can be find easily out

of 1000s.

Required less human effort. Low human error ratio. Low percentage of data losses. The backup of every employee record is also secured. Reduce employee cost, liability and admin burden through integrated solution.

The new computerized system is necessary to improve performance,

information, economics, security, efficiency, service, precision and accuracy.


3/127



1.2.4 Customer or Market Needs

By making the new desktop-application the requirement and needs of users (employee) are

fulfilled. The major needs of users were improve performance, information, economics,

security, efficiency, service, precision and accuracy. That was never possible in previous working

environment. In the new system the previous problems are solved.

1.3Vision of the solution1.3.1 Vision statementThe processing of information has been one of the basic tasks of every civilization .because of

the economic & population growth there are ever increasing needs to administrate large

quantities of interrelated data for administrative purposes.

Today the data processing system of an organization may be an old fashioned one with a clerk

entering the data processing system of an organization may be a modern one with the latest

computer hardware and software running round the clock and an expert team of IT professionals

always ready to face challenges of this highly competitive business world. The basic goal is

always same i.e. to provide the correct information to the authorized person at right time, at right

place and at right cost. Human Resources Management system has become vial for every

organization.

There are many overheads of manual system like inconsistency, lack of accuracy and precision,

lack of data updating, improper shifting of data into accounting cycle etc. Solution of all these

problems lies under the scope of our project.

The project desktop based application for employee Management system will replace the

current manual system of WASA.

The project employee management system constitutes of the following modules.

New Record of employee(personal info, job, qualification) Email system Inquiry Court cases Leave Report Print Search Delete record & Update record


4/127



This system will produce customized report for decision making by the higher management. It

will produce different analysis report for higher management. The output from the main

employee management system will serve as input for sub modules thus avoiding the duplication

of data and providing the accurate, in-time information and employee related documents.

1.4 Overall Description1.4.1 Product perspective

The main objective of this project is to develop a data base system to

fulfill the requirement of end users, management & employees.

In the manual system, for the process of different entries have to be entered intorelated registered which require a lot of time. The proposed system will save

much of time as its different segment will be integrated.

The manual system a lot of staff and stationary for keeping the record and allcollection of data. Our developed system will be economical. It will minimize all

the above-mentioned expenses.

In the existing there is possibility of the loss of data but in new computerizedsystem data will be stored in such a way that there is no chance of its loss. Data

will be centralized and will not allow irrelevant DML operation by unauthorized

users.

In the existing system there is no mechanism for backup & recovery of data incase of loss but in computerized system data will be back up on daily basis and

efficient algorithms will be used to recover the data in case of data lost. The proposed system will provide the facility of retrieving the data with accuracy

and superhuman speed.

This software will be so easy and convenient to use that he/she can enter andretrieve data very easily and friendly.

Furthermore it emphasized on:

Data security and safety. It will provide bird eye view of whole process to the management. It will save the time and the resources for generating report & other

official, unofficial documents.

It will minimize chances of errors thus providing accurate, efficient and intime documents needed for the process of export.

It will be highly flexible and cloud be easily enhanced with changingrequirements of employee management system.


5/127



It will be easily integrated with other system, i.e. costing system, accounts& finance systems of the WASA if needed in future.

This software will help the management to perform the complex analysisin a very simple, user friendly and easy way thus directly affecting the

performance and growth of the WASA.

1.4.2 Operating EnvironmentAfter doing the complete study of existing system and taking in view the shortcomings it is

necessary to refine the system by removing the deficiencies. It is needed to build a new system

according to the requirements of WASA. Hence an SQL based computerization system is

selected which will improve the currently manual system.

Database is designed in SQL server 2008 r 2. Forms are built in C# environment. Report is also design in C#.

1.4.3 User DocumentationFor developing desktop based application of WASA managing staff help us and provide

material about WASA employee. We get some information from concerning websites.

For designing of database different tutorials also helped us.

1.4.4 Assumption and Dependencies The database will be accessible in real time.

Initially our system manages only the work of WASA. Only managing person of WASA has the rights of any modification in database. Sql runtime software must be installed on the computer of end user. Database server could be accessible through internet from the remote distance. User must have the rights to use the application.

1.5 Project Life CycleWe select waterfall process model for system development.

Reasons to use:

By far the most commonly used approach up to now.All the most widely used methods are underpinned by the waterfall model.The stages are clear cut.


6/127



The original thinking behind it was that documents (tangible outputs) are produced ateach stage.

Consequently favored by top-management as easy to manage.All R&D done before coding start implies better quality program design.Well suited for developing stable, well understood web-based applications. For smaller software products shorter time from requirements to product completion.When a clear cut goal of the product is reached before the process begins.Requirements less likely to change

Requirements

Design

Implementation

Verification

Maintenance


7/127



CHAPTER -2

Requirements Specifications

2.1. Introduction

A software requirement specification is a complete of the behavior of system to be developed.

The software requirements specification begins the translation process that converts the software

requirement into language to developers will use.

With respect to our project this chapter includes:

1. System features2. External interface requirements3. Other non-functional requirements

2.2. System Features

The current system of WASA becomes useful by including some features. These features are:

2.2.1. Main Form:

a) Description and priority:

Main form provides the security to application and authentication the user i.e. whether its

authorized user or not. Every user has its own username and password.

b) Functional Requirements:

Main window

Application has the main window which will provide user interface. This window contains two

input fields for username and password and buttons for login and change password.

Login:

Login requires username and password if both are typed correctly the application show its menu

page. From the menu page any form or report can be executed.


8/127



Change password:

Clicking change password button another form will be open. Users provide their old password

with new one then click on change password button results the change in password.

New Record:

Clicking on the new record button a form will be open in which we enter the record of new

employee. If any field of this form is empty the software will not save the record. In new record

form we must want three requirement of employee.

1. Personal information2. Job qualification3. Qualification information

Inquiry:

Clicking on the inquiry button a form will be open in which we enter the inquiry record of

employee. If any employee has an allegation then this allegation will be save in his inquiry form

record.

Court Cases:

Clicking on the court cases button a form will be open in which we enter the court cases of any

employee. If any employee has any court case then this record of court case will be save in court

cases form.

Leaves:

Clicking on the leave button a form will be open in which we enter the leaves of any employee.

You cannot check the leave record of any employee until you enter the CNIC number of an

employee. It also saves the leaves record of the employees.

Training:

Clicking on the training button a form will be open in which we enter the training record of any

employee. In training form we enter the starting date when an employee start the training session

an when it ends we enter the ending date of training.

Update:


9/127



Clickings on the update button a form will be open in which we update the employee record.

Only the HEAD of the WASA update the employee record.

Delete:

Clicking on the delete button a form will be open in which we delete the employee record. Only

the HEAD of the WASA delete the employee record.

Search:

Clicking on the search button a form will be open in which we search the employee record. In

search form we define some categories to search the employee record.

Report:

Clicking on the report button a form will be open in which we open the reports of any employee.

We generate the daily basis report of the employees.

Email:

In email form we have some requirements to send the email to any employee.


10/127



Requirement #1

Login:

Requirement # Req-01 Requirement type: Functional

Description In this requirement, Data operator enters in systemby entering user name and password. To login Dataoperator must enter user name and password. This

can be match or not with database. If the id andpassword match with database we will loginsuccessfully.

Rationale

Source

Fit Criterion Operator will be successfully login.

Customer Satisfaction: Customer Dissatisfaction:

DependenciesSupporting Materials:


11/127



Requirement #2

Change Password:


Description In this requirement, sometimes due to security

failures we can loss our password, for which itbecomes necessary to change password to

defend WASA.

Rationale

Source

Fit Criterion Password will be successfully changed.


Dependencies

Supporting Materials:


12/127



Requirement # 3

New Record:


Description In this requirement, we recruit some of new

employees. It is necessary to enter all required

record in our data base.

Rationale

Source

Fit Criterion New Record of the employee will be saved.


Dependencies



13/127



Requirement # 4

Inquiry:


Description In this requirement, employee record is

verified due to some allegations. In which we

check the employee previous record, hisexperience, his attitude with organization e.t.c.

Rationale

Source

Fit Criterion Employee is successfully inquired.




14/127



Requirement # 5

Court cases:


Description In this requirement, the employee which is

offended is represented in front of higher

authorities who take decisions about theirfuture working in organization.

Rationale

Source

Fit Criterion Employee is represented in front of court.




15/127



Requirement # 6

Leaves:


Description In this requirement, employees are given

leaves on the basis of their throughout carrier

leaves, their yearly leaves or on the basis oftheir monthly leaves.

Rationale

Source

Fit Criterion Employees are granted by leaves.




16/127



Requirement # 7

Update:


Description In this requirement, data is revised on the basis

of changes in organization that change may be

in form of salary, designation or job rotations.

Rationale

Source

Fit Criterion Data is updated successfully.


Dependencies



17/127



Requirement # 8

Delete:


Description In this requirement, the un appropriate data

which is not in use is deleted from the data

base. This removal can be the elimination ofrecord of employee who has left the

organization.

Rationale

Source

Fit Criterion Un appropriate Data is deleted successfully.

Customer Satisfaction: Customer Dissatisfaction:Dependencies



18/127



Requirement # 9

Search:


Description In this requirement, we can check detail

information of our employee leaves, over time.

Our court cases, inquires and other issues facedby organization.

Rationale

Source

Fit Criterion Data is searched successfully.




19/127



Requirement # 10

Report:


Description In this requirement, reports are generated.

These reports can be based on our daily

performance. It may include any other recordwhich we required.

Rationale

Source

Fit Criterion Report is searched successfully.




20/127



Requirement # 11

Email:


Description In this requirement, all the necessary

information is emailed to all the employees of

our organization.

Rationale

Source

Fit Criterion Email sends successfully.


Dependencies



21/127


22/127



2.2.2. Information/management System


Information system provides the facility of management the record of employees. Our new

system introduce a new bio data from having many mandatory fields including personal

information, educational background, job information etc.

b) Functional Requirements:

Form Selection

Application has the two major categories of input forms as setup forms for setup data.

Transactional form for detailed information. Setup data is used in transactional form.

Setup forms

Setup form are used to save core information like cities name, designations etc.

Setup data once entered and rapidly used in transactional form in the form of LOV (list of

values).

Transaction Forms

These forms include bio data/record, designation wise employee r employee other record.

2.2.3. Reports


This system is generating different types of reports. Complete list of employee with their bio

data/record. Different types of reports generated by the employee management system. Reports

are generated in PDF format.

c) Functional Requirements:

Adobe redder software must be installed because reports will be generated in PDF format. User

can specify a location/folder for print to file option in reports. So user can save reports in a

specific directory.


23/127



Parameter Reports

Required values must be entered in specific format correctly.

2.3 External Interface Requirements

2.3.1 User Interfaces

User interface is used to provide communication between user and system. User interface is user

friendly and very easy to learn. All action and queries against each button is performed correctly.

Some user interfaces of new desktop based application are:

New Record of employee form(personal info, job, qualification) Email system

Inquiry Court cases Leave Report Print Search Delete record & Update record

2.3.2 Hardware Interfaces

Desktop based employee management system for WASA is Sql server dependant. Our hardware

includes:

Tool Requirement

Processor dual core Minimum 1GB RAM 80GB hard disk or greater

Database Requirement

Pentium III or higher 512 RAM or higher 80 GB of hard disk Dual core processor


24/127



2.3.3 Software Interfaces

During implementation of effective employee management system (EMS) solution, following

tools have been used:

Microsoft windows 2007/XP professional Edition.

SQL VB.net C#

The reasons for using these tools and operating system have been given below:

SQL is a flexible, easiest and most productive language. MS windows XP is one of the best operating systems equipped with better security,

interfaces and recovery techniques.

VB.net is very user friendly interface designing software.2.3.4 Communication Interfaces

The front end of the system is directly concerned with the end users. It consists of user interfaces

and forms. We have developed it using c# form builder. For communication with database server

following installation are required:

Vb.net C# SQL server 2008 R2

2.4. Other Nonfunctional Requirements

2.4.1 Performance Requirements

New system performs best services even though many number of users requested the different

desired services.SQL server can response within seconds even simultaneously more than

500users send entirely different requests.

Twenty-four hour availability Peak usage across all time zones Complete database recovery

2.4.2 Safety Requirements

There must be power of backup for data base server.


25/127



Describe user-managed backup and recovery operations. Perform closed database backup. Backup the control files. Use DB VERIFY utility to verify the backups and to detect corruption.

2.4.3 Security Requirements

In Microsoft access based system there was no reliable security measures. Chances of loss of

data and damage of information were high. New system provides security from deliberate

accidental damage or access by unauthorized persons. Each data operator has given access to

required table and views by assigning privileges and roles.

The ability to natively encrypt data in the SQL Database enables applications to guard their

sensitive data, even if unwanted intruders gain access to the server.

2.4.4 Software Quality Attributes

In our application database server is never accessible by any user. But administration

can easily update and maintain the database. Because of that some software quality

attributes of new system are:

Adaptable Availability Correctness Flexibility Maintainability Portability Reliability Reusability

2.4.5 Other Requirements

Database Requirements:

The system use SQL database that provides advanced security to client-server and server-server

network security using encryption and data integrity, and support enhanced user authentication

services. An SQL architecture includes number of primary components:

SQL server 2008 R2 SQL database Other key files User and server processes


26/127



CHAPTER-3

System Architecture

3.1 Introduction

Our product for WASA employee management system has been developed using three tier

architectural model. Overview of each tier has been given below:

3.1.1 Front Tier

The front end of the system is directly concerned with the end users. It consists of user interfaceand forms. we have developed it using vb.net and c.# form builder.

3.1.2 Middle Tier

This tier is purely concerned with the core of the project that is business logic; all the

programming has been accomplished SQL server. This tier acts as bridge between the front end

and back end.

3.1.3 Information Tier

This tier is related to the database management system. SQL server 2008 R2 has been used forthis purpose.

All the relationships between these tier has been shown in this diagram:

Actor1

Front Tier

(End User)

Middle Tier

(Business User)

Information

Tier (DBMS)

Database


27/127



3.2Analysis and DesignThe abstract use case model of system is shown here that gives an abstract overview of

system functionalities.


28/127




29/127



3.2.1 Description of Each Use Case

Use Case Name: Login

UC # 01 Ref: Req. # 01UC Name Login

Level Abstract

Description In this module, Data operator must enter user

name and password to login. This can be match

or not with database. If the id and passwordmatch with database we will login

successfully.

Actor (S) Data operator

Stakeholder DO, Administrator

Preconditions

Success Guarantee User login successfully and main interfacedisplay for data operator.

Main Success Scenario

Action System Response

1. DO provide login

id and password.

2. Main interface will

be opened.

Extensions 1a.Invalid data entry. System asks to re-enter wrong entry.

Special Requirements No special requirement

Frequency of Occurrence As per requirement

Miscellaneous No


30/127



Use Case Name:Change Password

UC # 02 Ref: Req. # 02UC Name Change Password

Level Abstract

Description In this module, sometimes due to security

failures we can loss our password, for which it

becomes necessary to change password todefend WASA.


Stakeholder DO, Administrator, Employee, Guest

Preconditions

Success Guarantee Password will be successfully changed.

Main Success ScenarioAction System Response1. DO changes thepassword.

2. system change thepassword

successfully.

Extensions 1a.Invalid data entry. System asks to re-

enter wrong entry.



Miscellaneous No


31/127



Use Case Name:New Record

UC # 03 Ref: Req. # 03UC Name New Record

Level Abstract

Description In this module, we recruit some of new

employees. It is necessary to enter all required

record in our data base.



Preconditions

Success Guarantee New Record of the employee will be saved.



1. DO save the recordof new employee.

2. system successfullysave the record.


enter wrong entry.



Miscellaneous No


32/127



Use Case Name:Inquiry

UC # 04 Ref: Req. # 04UC Name Inquiry

Level Abstract

Description In this module, employee record is verified due

to some allegations. In which we check the

employee previous record, his experience, hisattitude with organization e.t.c.



Preconditions

Success Guarantee Employee is successfully inquired.

Main Success ScenarioAction System Response1. DO saves theinquiry record of the

employees.

2. system successfullysaves the inquiry

record.


enter wrong entry.



Miscellaneous No


33/127



Use Case Name:Court Cases

UC # 05 Ref: Req. # 05UC Name Court Cases

Level Abstract

Description In this module, the employee which is

offended is represented in front of higher

authorities which take decisions about theirfuture working in organization.



Preconditions

Success Guarantee Employee is represented in front of court.

Main Success ScenarioAction System Response1. DO saves the courtcases record of the

employees.

2. system successfullysaves the court cases

record.


enter wrong entry.



Miscellaneous No


34/127



Use Case Name:Leaves

UC # 06 Ref: Req. # 06UC Name Leaves

Level Abstract

Description In this module, employees are given leaves on

the basis of their throughout carrier leaves,

their yearly leaves or on the basis of theirmonthly leaves.



Preconditions

Success Guarantee Employee are granted by leaves.

Main Success ScenarioAction System Response1. DO saves theleaves record of the

employee.

2. system successfullysaves the leaves

record.


enter wrong entry.



Miscellaneous No


35/127



Use Case Name:Update

UC # 07 Ref: Req. # 07UC Name Update

Level Abstract

Description In this module, data is revised on the basis of

changes in organization that change may be in

form of salary, designation or job rotations.



Preconditions

Success Guarantee Data is updated successfully.



1. DO update theemployee record.

2. system successfullyupdate record.


enter wrong entry.



Miscellaneous No


36/127



Use Case Name:Delete

UC # 08 Ref: Req. # 08UC Name Update

Level Abstract

Description In this module, the un appropriate data which

is not in use is deleted from the data base. This

removal can be the elimination of record ofemployee who has left the organization.



Preconditions

Success Guarantee Un appropriate Data is deleted successfully.

Main Success ScenarioAction System Response1. DO delete the unappropriate data of the

employee.

2. system successfullydelete record.


enter wrong entry.



Miscellaneous No


37/127



Use Case Name:Search

UC # 09 Ref: Req. # 09UC Name Search

Level Abstract

Description In this module, we can check detail

information of our employee leaves, over time.

Our court cases, inquires and other issues facedby organization.



Preconditions

Success Guarantee Data is searched successfully.

Main Success ScenarioAction System Response1. DO search theemployee record.

2. system successfullysearch record.


enter wrong entry.



Miscellaneous No


38/127



Use Case Name:Report

UC # 10 Ref: Req. # 10UC Name Report

Level Abstract

Description In this module, reports are generated. These

reports can be based on our daily performance.

It may include any other record which werequired.



Preconditions

Success Guarantee Report is generated successfully.

Main Success ScenarioAction System Response1. DO generate thereport of the

employee on daily

basis.

2. system successfullygenerate report.

Extensions 1a.Invalid data entry. System asks to re-enter wrong entry.



Miscellaneous No


39/127



Use Case Name:Email

UC # 11 Ref: Req. # 11UC Name Email

Level Abstract

Description In this module, all the necessary information is

emailed to all the employees of our

organization.



Preconditions

Success Guarantee Email sends successfully.



1. DO sends the emailto the employees.

2. system successfullysends mail.


enter wrong entry.



Miscellaneous No


40/127



3.3 System Sequence Diagram

To a Login User:

DO

Do come in to system

System show login interface

Do enter user name and password

System show main interface

System


41/127



Change Password:

DO

DO come in to system


DO click on change password button

System show change password interface

DO enter Old and new password

System show change password message

System


42/127



New Record:

DO

Do come in to system and login


Do Click new record button

System show new record form

Do operator enter new record and press save button

System Show message to Save Record

System


43/127



Inquiry:

DO



Do Click inquiry button

System show inquiry form

Do operator enter inquiry record and press save button

System Show message to Save inquiry record

System


44/127



Court Cases:

DO



Do Click court cases button

System show court cases form

Do operator enter court cases record

System Show message to save court cases record

System


45/127



Leaves:

DO


System show Leaves interface

Do Click Leaves button

System show Leaves form

Do operator enter Leaves record

System Show message to save Leaves record

System


46/127



Training:

DO


System show training interface

Do Click training button

System show training form

Do operator enter training record

System Show message to save training record

System


47/127



Update:

DO


System show update interface

Do Click update button

System show update form

Do operator enter update record

System Show message to save update record

System


48/127



Delete:

DO


System show delete interface

Do Click delete button

System show delete form

Do operator enter delete record

System Show message to save delete record

System


49/127



Search:

DO


System show Search interface

Do Click Search button

System show search form

Do operator enter search record

System Show message to search record

System


50/127



Report:

DO


System show report interface

Do Click report button

System show report

Do operator generate report

System Show message to generate report

System


51/127



Email:

DO


System show email interface

Do Click email button

System show requirement to send mail

Do operator sending mail

System Show message to send mail

System


52/127



3.4 Sequence Diagrams

Login sequence diagram:

DO

Do come in to system interface


Do enter user name and password

System verify user name and password

Verify

Database sends result after verification

System interface show main interface

System

Interface

Database


53/127



Change password sequence diagram:

U

DO



DO click on Change Password button

System show change password interface

Do enter old and new password

System request for verify old password In DB

Verify

Database sends result after verification

System show Change password Message

System

Interface

Databa


54/127



New Record:

DO


System shows New Record interface

Do enter require Data in Field

System request to save New Record

Verify

Response about save New Record

System show save new record message

System

Interface

Database


55/127



Inquiry:

DO


System show Inquiry interface

Do enter require Data in Field

System request to save inquiry record

Verify

Response about save inquiry record

System show inquiry record save message

System

Interface

Databa


56/127



Court Cases:

DO


System show court cases interface

Do enter require Data to save court cases

System request to save court cases record

Verify

Response about save court cases record

System show court cases record message

System

Interface

Databa


57/127



Leaves:

DO


System shows Leaves interface

Do enter require Leaves record

System request to save Leave record

Verify

Response about save Leaves record

System show save Leaves record message

System

Interface

Database


58/127


59/127



Update:

DO


System shows Update interface

Do enter require Update record

System request to save Update record

Verify

Response about save Update record

System show save Update record message

System

Interface

Database


60/127



Delete:

DO


System shows Delete interface

Do enter Delete record

System request to Delete record

Verify

Response about Delete record

System show Delete message

System

Interface

Database


61/127


62/127



Report:

DO


System shows Report interface

Do generate report of employee record

System request to generate report

Verify

Response about generate report

System show report generate message

System

Interface

Database


63/127


64/127



3.5 ERD Model:


65/127


66/127



Functional Testing:

Test Cases Test Case Description Result

1. Check all buttons

that helps user tonavigate from one page

to another.

All buttons

successfullyperformed their

functions.

2. All data entry

operations checked by

entering data.

All data entry

operations

successfullyperformed their

functionalities.

3. Checked any other

functions for example

update data buttons.

All other functions

perform their

functionalities.

Completion Criteria All functions are successfully performed their

functionalities.


67/127



User Interface Testing:

Test Objective Our main objective of this is to check

navigation including window to window, field

to field and use of access methods e.g. tab keys,

mouse movements, and other keys. We alsofocus on other characteristics like menus, size,

positions, state, colors and any such other

characteristics.


1. Every user interface

is checked one by one.

All characteristics

that described abovefulfill by every user

interface.

Completion Criteria Tab key, esc key work properly. Mouse

movement is ok. Colors are professional and

text color is ok and text is easily readable.Navigation among pages also ok.

Special Consideration Nothing.


68/127



Performance Testing:

Test Objective Our main objective of this is to check that whenusers enter data, modify data, and delete data

whether the response showed in proper time or

not. What happens when a lot number of requests

come to server?

Test Cases Test Case Description Result1. When a lot number of

requests come todesktop server.

Because wide zone

international has itsown server so these

requests will be

fulfilled in proper time.

2. When user enter,

modify, delete data.

Web server and

database server

response quickly.

Completion Criteria If a single or multiple data entry operations at a

time delete modify enters data then there is no

restriction for this and data successfully modified

and entered.

Special Consideration The web server and database server should havecapability to response at least 8000 to 15000 usersat a time


69/127



Login Testing:

Test Objective Our main objective of this is to check that whenusers enter user name and password whether the

response shown in proper or not.


1. When a lot number

of requests come to

server.

Because wide zone

international has its

own server so these

requests will befulfilled in proper

time.2. When user enter,

valid user name and

password.

User as granted

access to its account.

3. A wrong user name

or password is entered.

System show error

message.

4.If user click onremain login tab.

User will remainlogin

Completion Criteria All buttons belongs to login section are

functioning properly. Therefore no need toworry about login section. No invalid user can

gain access to any other account.

Special Consideration The web server and database server should be

in running mode.


70/127



Change Password Testing:

Test Objective Our main objective of this is to check that whenuser change the password of the system, then

the system successfully change the password or

not?


1. when the user

change the password.

System response, the

password

successfully changed.Completion Criteria If the user change the password of the system

the password must successfully changed andsystem should response quickly and all its

functionately work properly.



71/127



New Record Testing:

Test Objective Our main objective of this is to check that whena new employee has join the organization the

user entered the data of this employee in the

system then the system save the record

successfully or not?


1. When user enter the

record of the employee.

System save the

record successfully.

2. When user left some

fields of form.

System shows the

error message.

Completion Criteria If the user enter the record of the employee thesystem save the record quickly and there is no

restriction for this and data successfully save.

Special Consideration If any field of the form is empty then data is not

saved.


72/127



Update Record Testing:

Test Objective Our main objective of this is to check that whenusers update the data of the employee the

system response us in proper time or not and

data is updated or not?


1. When user update

the record of the

employee.

System update the


2. When user enter

wrong information ofthe employee.

System shows the

error message.

Completion Criteria If the user update the record of the employeethe system must the update record of the

employee in proper time and there is no

restriction to update record.

Special Consideration The head of organization login to update the

record.


73/127



Delete Record Testing:

Test Objective Our main objective of this is to check that when

users delete the data of the employee, the

system response us in proper time or not anddata is deleted or not?


1. When user delete the

record of the employee.

System delete the


Completion Criteria If the user delete the record of the employee the

system must delete the record of the employeein proper time and there is no restriction to

delete record.

Special Consideration The head of organization login to delete the

record.


74/127



Report Generate Testing:


users generate the report of the employee on

daily basis the system response us in proper

time or not and report is generated or not?


1. When user generate

the report of the

employee.

System generate the

report successfully.

2. When user generatethe wrong report.

System shows theerror message.

Completion Criteria If the user generate the report of the employee

the system must the generate the report of the

employee in proper time and there is norestriction to generate report.



75/127



Email Testing:


users email some information of the

organization to the employee the system sends

the mail in proper time or not?


1. When user sends the

email to the employees.

System sends the

mail successfully.

2. When user enterwrong ID of the

employee.

System shows theerror message.

Completion Criteria If the user sends the email to the employees the

system sends the mail in proper time to the

employees. There is no restriction to sendingthe mail.



76/127



CHAPTER-5

User Manual and Coding:

Employee management system is very user friendly software. All the menus, forms and options

are very easy to use. This manual describes how different forms can be used and how they

behave. The use of dialogue boxes and use of different buttons are described in details in this

manual. Also the use and purpose of all links of button to required form be described.

Login:


77/127



Change Password:


78/127



Departments and Global Search Form:


79/127



New Record Form:


80/127


81/127



Court Cases Form:


82/127



Leaves Form:


83/127



Training Form:


84/127



Update Record Form:


85/127


86/127



Search Form:


87/127



Reports:


88/127



Email Form:


89/127



Code:

Main FormusingSystem;

usingSystem.Collections.Generic;usingSystem.ComponentModel;

usingSystem.Data;usingSystem.Drawing;usingSystem.Linq;

usingSystem.Text;

usingSystem.Windows.Forms;

namespaceFDA_EHRM

{

publicpartialclassMainForm: Form{

publicMainForm()

{ InitializeComponent();}

privatevoidbuttonCancel_Click(objectsender, EventArgse)

{this.Close();

}

privatevoidbuttoncancel_Click_1(objectsender, EventArgse){

Departmentsdep = newDepartments();

dep.Show();

this.Hide();}

privatevoidbuttonnewrecord_Click(objectsender, EventArgse){

newrcccnewrecord = newnewrccc();

newrecord.Show();this.Hide();

}

privatevoidbuttonupdate_Click(objectsender, EventArgse)

{

updatepassword1updatep1 = newupdatepassword1();updatep1.Show();


90/127


91/127



privatevoidbutton4_Click(objectsender, EventArgse)

{Trainingtrning = newTraining();

trning.Show();

this.Hide();}


{errorcasenewrecordsut = newerrorcasenewrecord();

sut.Show();

this.Hide();

}


{ leaveleav = newleave();

leav.Show();

this.Hide();

}

}

}

New Record

usingSystem;usingSystem.Collections.Generic;

usingSystem.ComponentModel;

usingSystem.Data;usingSystem.Drawing;

usingSystem.Linq;

usingSystem.Text;usingSystem.Windows.Forms;

usingSystem.Data.SqlClient;

usingSystem.Management;

usingFDA_db;usingSystem.Collections;

usingSystem.Configuration;

namespaceFDA_EHRM

{publicpartialclassnewrccc: FDA_EHRM.MainForm

{

Connectionconc = newConnection();


92/127



privateinti;

privateintii;

privateSqlConnectionMyConnection = null;privateSqlCommandMyCommand = null;

privateSqlDataAdapterMyAdapter = null;

privateSqlDataReaderdr = null;privateDataSetMyDataset = newDataSet();publicnewrccc()

{

InitializeComponent();this.datetime.Text = Convert.ToString(dateTimePicker1.Value);

}

privatevoidbutton16_Click(objectsender, EventArgse){

}


if(this.name.Text == " "|| this.cnic.Text == ""|| this.job_nature.Text == " "||

this.Designations.Text == ""){

MessageBox.Show("Please Fill The Empty OR Require Filed");

}else

{

conc.SaveRecord("insert into admin_newinfo_tb values ('"+ File_no.Text + "','"+

rec_no.Text + "','"+ datetime.Text + "','"+ name.Text + "','"+ fathername.Text + "','"+cnic.Text + "','"+ city.Text + "','"+ province.Text + "','"+ nationality.Text + "','"+ domicle.Text

+ "','"+ age.Text + "','"+ dob.Text + "','"+ paddress.Text + "','"+ taddress.Text + "','"+

eaddress.Text + "','"+ mnumber.Text + "','"+ pnumber.Text + "','"+ enumber.Text + "','"+male.Text + "','"+ marital_st.Text + "','"+ yes.Text + "','"+ muslim.Text + "','"+ "','"+

job_nature.Text + "','"+ departments.Text + "','"+ Designations.Text + "','"+ dojs.Text + "','"+

pops.Text + "','"+ dopips.Text + "','"+ pay_scale.Text + "','"+ m_boards.Text + "','"+m_grades.Text + "','"+ m_ages.Text + "','"+ m_cgpas.Text + "','"+ m_sessions.Text + "','"+

i_boardss.Text + "','"+ i_gradess.Text + "','"+ i_agess.Text + "','"+ i_cgpass.Text + "','"+

i_sessionss.Text + "','"+ g_boards.Text + "','"+ g_grades.Text + "','"+ g_ages.Text + "','"+

g_cgpas.Text + "','"+ g_sessions.Text + "','"+ p_boards.Text + "','"+ p_grades.Text + "','"+p_ages.Text + "','"+ p_cgpas.Text + "','"+ p_sessions.Text + "','"+ o_boards.Text + "','"+

o_grades.Text + "','"+ o_ages.Text + "','"+ o_cgpas.Text + "','"+ o_sessions.Text + "')");

this.i = Convert.ToInt32(this.File_no.Text);

i++;this.File_no.Text = Convert.ToString(this.i);

name.Text = null;

fathername.Text = null;cnic.Text = null;


93/127



city.Text = null;

province.Text = null;

nationality.Text = null;domicle.Text = null;

age.Text = null;

dob.Text = null;paddress.Text = null;taddress.Text = null;

eaddress.Text = null;

mnumber.Text = null;pnumber.Text = null;

enumber.Text = null;

job_nature.Text = null;

departments.Text = null;Designations.Text = null;

dojs.Text = null;

pops.Text = null;dopips.Text = null;

pay_scale.Text = null;

m_boards.Text = null;

m_grades.Text = null;m_ages.Text = null;

m_cgpas.Text = null;

m_sessions.Text = null;i_boardss.Text = null;

i_gradess.Text = null;

i_agess.Text = null;

i_cgpass.Text = null;i_sessionss.Text = null;

g_boards.Text = null;

g_grades.Text = null;g_ages.Text = null;

g_cgpas.Text = null;

g_sessions.Text = null;p_boards.Text = null;

p_grades.Text = null;

p_ages.Text = null;

p_cgpas.Text = null;p_sessions.Text = null;

o_boards.Text = null;

o_grades.Text = null;

o_ages.Text = null;o_cgpas.Text = null;

o_sessions.Text = null;

}}


94/127




{name.Text = null;

fathername.Text = null;

cnic.Text = null;city.Text = null;province.Text = null;

nationality.Text = null;

domicle.Text = null;age.Text = null;

dob.Text = null;

paddress.Text = null;

taddress.Text = null;eaddress.Text = null;

mnumber.Text = null;

pnumber.Text = null;enumber.Text = null;

}


{job_nature.Text=null;

departments.Text = null;

Designations.Text = null;

dojs.Text = null;pops.Text = null;

dopips.Text = null;

pay_scale.Text = null;}


m_boards.Text = null;

m_grades.Text = null;

m_ages.Text = null;m_cgpas.Text = null;

m_sessions.Text = null;

i_boardss.Text = null;

i_gradess.Text = null;i_agess.Text = null;

i_cgpass.Text = null;

i_sessionss.Text = null;g_boards.Text = null;


95/127



g_grades.Text = null;

g_ages.Text = null;

g_cgpas.Text = null;g_sessions.Text = null;

p_boards.Text = null;

p_grades.Text = null;p_ages.Text = null;p_cgpas.Text = null;

p_sessions.Text = null;

o_boards.Text = null;o_grades.Text = null;

o_ages.Text = null;

o_cgpas.Text = null;

o_sessions.Text = null;}

privatevoidnewrccc_Load(objectsender, EventArgse){

MyConnection = newSqlConnection();

stringConString = "Data source=.; initial catalog=FDA_db; Integrated Security= SSPI";

MyConnection.ConnectionString = ConString;MyConnection.Open();

MyCommand = newSqlCommand("select File_no from admin_newinfo_tb ORDER BY

File_no", MyConnection);//MyCommand.ExecuteNonQuery();

dr = MyCommand.ExecuteReader();

if(dr.HasRows)

{while(dr.Read())

{

File_no.Text = dr["File_no"].ToString();}

}

MyConnection.Close();


i++;

this.File_no.Text = Convert.ToString(this.i);}


{OpenFileDialogupload = newOpenFileDialog();

upload.Filter = "Image Files(*.jpg;*.jpeg;*.gif;*.bmp;)|*.jpg;*.jpeg;*.gif;*.bmp";

upload.InitialDirectory = @"C:\";if(upload.ShowDialog()==DialogResult.OK)


96/127



{

pictureBox2.Image = Image.FromFile(upload.FileName);

}

}

privatevoidimage_Click(objectsender, EventArgse)

{

}

}

}

Inquiry



usingSystem.Data;

usingSystem.Drawing;usingSystem.Linq;

usingSystem.Text;

usingSystem.Windows.Forms;usingSystem.Data.SqlClient;


usingFDA_db;

usingSystem.Collections;usingSystem.Configuration;

namespaceFDA_EHRM{

publicpartialclassInquiryForm: FDA_EHRM.MainForm

{Connectionconc=newConnection();

privateinti;

privateintii;


privateSqlDataAdapterMyAdapter = null;

privateSqlDataReaderdr = null;privateDataSetMyDataset = newDataSet();

publicInquiryForm()

{InitializeComponent();

this.datetime.Text = Convert.ToString(dateTimePicker1.Value);

}


97/127



privatevoidInquiryForm_Load(objectsender, EventArgse){

MyConnection = newSqlConnection();stringConString = "Data source=ZAHID-HAMEED-HP; initial catalog=FDA_db;Integrated Security= SSPI";

MyConnection.ConnectionString = ConString;

MyConnection.Open();MyCommand = newSqlCommand("select File_no from admin_inqury1_tb ORDER BY

File_no", MyConnection);

dr = MyCommand.ExecuteReader();if(dr.HasRows)

{

while(dr.Read()){

File_no.Text = dr["File_no"].ToString();

}

}


this.i = Convert.ToInt32(this.File_no.Text);i++;

this.File_no.Text = Convert.ToString(this.i);

}


if(cnic.Text == ""|| name_dsg.Text == ""|| brief_description.Text == ""|| rules.Text ==""|| pending.Text == ""|| name_dsg.Text == "")

{

MessageBox.Show("Plase Enter Data In Empty Filed");

}

else

{

conc.SaveRecord("insert into admin_inqury1_tb values ('"+ File_no.Text + "','"+rec_no.Text + "','"+ datetime.Text + "','"+ cnic.Text + "','"+ name_dsg.Text + "','"+

brief_description.Text + "','"+ rules.Text + "','"+ pending.Text + "','"+ under_action.Text +

"')");


98/127




i++;

this.File_no.Text = Convert.ToString(this.i);this.cnic.Text = null;

this.name_dsg.Text = null;

this.brief_description.Text = null;this.rules.Text = null;this.pending.Text = null;

this.under_action.Text = null;

}

}

privatevoidFile_no_Click(objectsender, EventArgse){

}}

}

Court Cases



usingSystem.Data;


usingSystem.Text;



usingFDA_db;usingSystem.Collections;


namespaceFDA_EHRM

{publicpartialclasscourt_cases: FDA_EHRM.MainForm

{

Connectionconc = newConnection();privateinti;privateintii;

privateSqlConnectionMyConnection = null;

privateSqlCommandMyCommand = null;privateSqlDataAdapterMyAdapter = null;

privateSqlDataReaderdr = null;

privateDataSetMyDataset = newDataSet();


99/127



publiccourt_cases()

{

InitializeComponent();this.datetime.Text = Convert.ToString(dateTimePicker1.Value);

}


if(cnic.Text == ""|| name.Text == ""|| title.Text==""){

MessageBox.Show("Plase Enter Data In Empty Filed");

}

else{

conc.SaveRecord("insert into admin_cases_tb values ('"+ File_no.Text + "','"+

rec_no.Text + "','"+ datetime.Text + "','"+ cnic.Text + "','"+ name.Text + "','"+Petitioner_date.Text + "','"+ title.Text + "','"+ versus.Text + "','"+ legal_advisor.Text + "','"+

case_description.Text + "','"+ current_progress.Text + "','"+ results.Text + "')");

}

}

privatevoidtextBox3_TextChanged(objectsender, EventArgse)

{

privatevoidcourt_cases_Load(objectsender, EventArgse)

{MyConnection = newSqlConnection();

stringConString = "Data source=ZAHID-HAMEED-HP; initial catalog=FDA_db;

Integrated Security= SSPI";MyConnection.ConnectionString = ConString;

MyConnection.Open();

MyCommand = newSqlCommand("select File_no from admin_case_tb ORDER BYFile_no", MyConnection);


if(dr.HasRows)

{while(dr.Read())

{


}}

MyConnection.Close();this.i = Convert.ToInt32(this.File_no.Text);


100/127



i++;


}

privatevoiddateTimePicker1_ValueChanged(objectsender, EventArgse)

{

}

}

}

Leave



usingSystem.Data;

usingSystem.Drawing;usingSystem.Text;


namespaceFDA_EHRM

{

publicpartialclassleave: FDA_EHRM.MainForm

{publicleave()

{

InitializeComponent();}


this.cleave.Text = "48";

this.yleave.Text = "25";

this.tleave.Text = "73";}


}

}}

Training


101/127



usingSystem;

usingSystem.Collections.Generic;

usingSystem.ComponentModel;usingSystem.Data;

usingSystem.Drawing;

usingSystem.Linq;usingSystem.Text;usingSystem.Windows.Forms;


usingSystem.Management;usingFDA_db;

usingSystem.Collections;


namespaceFDA_EHRM

{

publicpartialclassTraining: FDA_EHRM.MainForm{


privateinti;privateintii;


privateSqlCommandMyCommand = null;privateSqlDataAdapterMyAdapter = null;


privateDataSetMyDataset = newDataSet();

publicTraining(){

InitializeComponent();

this.datetime.Text = Convert.ToString(dateTimePicker1.Value);}


if(cnic.Text == ""|| name.Text == ""|| starting_date.Text == ""|| Ending_date.Text ==

""|| Subject.Text == ""|| given_by.Text == ""|| department.Text==""||venue.Text=="")

{MessageBox.Show("Plase Enter Data In Empty Filed");

}

else{

conc.SaveRecord("insert into admin_training_tb values ('"+ File_no.Text + "','"+

rec_no.Text + "','"+ datetime.Text + "','"+ cnic.Text + "','"+ name.Text + "','"+


102/127



starting_date.Text + "','"+ Ending_date.Text + "','"+ Subject.Text + "','"+ given_by.Text + "','"

+ department.Text + "','"+ venue.Text + "')");


i++;

this.File_no.Text = Convert.ToString(this.i);this.cnic.Text = null;this.name.Text = null;

this.starting_date.Text = null;

this.Ending_date.Text = null;this.Subject.Text = null;

this.given_by.Text = null;

this.department.Text = null;

this.venue.Text = null;

}

}

privatevoidTraining_Load(objectsender, EventArgse)

{

MyConnection = newSqlConnection();stringConString = "Data source=ZAHID-HAMEED-HP; initial catalog=FDA_db;

Integrated Security= SSPI";

MyConnection.ConnectionString = ConString;MyConnection.Open();

MyCommand = newSqlCommand("select File_no from admin_training_tb ORDER BY

File_no", MyConnection);


if(dr.HasRows)

{while(dr.Read())

{

File_no.Text = dr["File_no"].ToString();}

}

MyConnection.Close();this.i = Convert.ToInt32(this.File_no.Text);

i++;


}}

}

Save Update


103/127



usingSystem;

usingSystem.Collections.Generic;

usingSystem.ComponentModel;usingSystem.Data;

usingSystem.Drawing;

usingSystem.Linq;usingSystem.Text;usingSystem.Windows.Forms;



usingSystem.Collections;


namespaceFDA_EHRM

{

publicpartialclasssaveupdatetraing: FDA_EHRM.MainForm{


privateinti;



publicsaveupdatetraing(){

InitializeComponent();

this.datetime.Text = Convert.ToString(dateTimePicker1.Value);

}


{MyConnection = newSqlConnection();

stringConString = "Data source=ZAHID-HAMEED-HP; initial catalog=FDA_db;

Integrated Security= SSPI";MyConnection.ConnectionString = ConString;


MyCommand = newSqlCommand("select

File_no,Record_no,CNIC,Name,Starting_date,Ending_date,Subject,Training_given_by,Department,Venue from admin_training_tb where CNIC='"+ cnic.Text + "' ", MyConnection);


if(dr.HasRows)

{while(dr.Read())

{

File_no.Text = dr["File_no"].ToString();rec_no.Text = dr["Record_no"].ToString();


104/127



cnic.Text = dr["CNIC"].ToString();

name.Text = dr["Name"].ToString();

starting_date.Text = dr["Starting_date"].ToString();Ending_date.Text = dr["Ending_date"].ToString();

given_by.Text = dr["Training_given_by"].ToString();

department.Text = dr["Department"].ToString();venue.Text = dr["Venue"].ToString();}

}


}


this.i = Convert.ToInt32(this.rec_no.Text);

i++;this.rec_no.Text = Convert.ToString(this.i);

conc.SaveRecord("insert into admin_training_tb values ('"+ File_no.Text + "','"+

rec_no.Text + "','"+ datetime.Text + "','"+ cnic.Text + "','"+ name.Text + "','"+

starting_date.Text + "','"+ Ending_date.Text + "','"+ Subject.Text + "','"+ given_by.Text + "','"+ department.Text + "','"+ venue.Text + "')");

}

}}

Save Update Training

usingSystem;

usingSystem.Collections.Generic;usingSystem.ComponentModel;

usingSystem.Data;


usingSystem.Text;


usingSystem.Data.SqlClient;usingSystem.Management;

usingFDA_db;


namespaceFDA_EHRM

{publicpartialclasssaveupdatetraing: FDA_EHRM.MainForm

{



105/127



privateinti;


privateSqlCommandMyCommand = null;privateSqlDataReaderdr = null;

publicsaveupdatetraing()

{ InitializeComponent();this.datetime.Text = Convert.ToString(dateTimePicker1.Value);

}


{


stringConString = "Data source=ZAHID-HAMEED-HP; initial catalog=FDA_db;Integrated Security= SSPI";


MyConnection.Open();MyCommand = newSqlCommand("select

File_no,Record_no,CNIC,Name,Starting_date,Ending_date,Subject,Training_given_by,Departm

ent,Venue from admin_training_tb where CNIC='"+ cnic.Text + "' ", MyConnection);

dr = MyCommand.ExecuteReader();if(dr.HasRows)

{

while(dr.Read()){


rec_no.Text = dr["Record_no"].ToString();

cnic.Text = dr["CNIC"].ToString();name.Text = dr["Name"].ToString();

starting_date.Text = dr["Starting_date"].ToString();

Ending_date.Text = dr["Ending_date"].ToString();given_by.Text = dr["Training_given_by"].ToString();

department.Text = dr["Department"].ToString();

venue.Text = dr["Venue"].ToString();}

}

MyConnection.Close();}


{

this.i = Convert.ToInt32(this.rec_no.Text);i++;

this.rec_no.Text = Convert.ToString(this.i);

conc.SaveRecord("insert into admin_training_tb values ('"+ File_no.Text + "','"+rec_no.Text + "','"+ datetime.Text + "','"+ cnic.Text + "','"+ name.Text + "','"+


106/127



starting_date.Text + "','"+ Ending_date.Text + "','"+ Subject.Text + "','"+ given_by.Text + "','"

+ department.Text + "','"+ venue.Text + "')");

}}

}

Save Inquiry

usingSystem;usingSystem.Collections.Generic;usingSystem.ComponentModel;

usingSystem.Data;usingSystem.Drawing;

usingSystem.Linq;

usingSystem.Text;



usingFDA_db;


namespaceFDA_EHRM{

publicpartialclassSave_update_inquiry: FDA_EHRM.MainForm

{

Connectionconc = newConnection();privateinti;


privateSqlCommandMyCommand = null;privateSqlDataReaderdr = null;

publicSave_update_inquiry()

{InitializeComponent();

this.datetimes.Text = Convert.ToString(dateTimePicker1.Value);

}


MyConnection = newSqlConnection();stringConString = "Data source=ZAHID-HAMEED-HP; initial catalog=FDA_db;

Integrated Security= SSPI";



107/127




MyCommand = newSqlCommand("select * from admin_inqury1_tb where CNIC='"+

cnic.Text + "' ", MyConnection);dr = MyCommand.ExecuteReader();

if(dr.HasRows)

{ while(dr.Read()){

File_nos.Text = dr["File_no"].ToString();

rec_nos.Text = dr["Record_no"].ToString();cnic.Text = dr["CNIC"].ToString();

name_dsg.Text = dr["Name_dsg"].ToString();

brief_description.Text = dr["Brief_description"].ToString();

rules.Text = dr["Rules"].ToString();pending.Text = dr["Pending"].ToString();

under_action.Text = dr["Action_taken"].ToString();

}}


}


{this.i = Convert.ToInt32(this.rec_nos.Text);

i++;

this.rec_nos.Text = Convert.ToString(this.i);

conc.SaveRecord("insert into admin_inqury1_tb values ('"+ File_nos.Text + "','"+rec_nos.Text + "','"+datetimes.Text + "','"+ cnic.Text + "','"+ name_dsg.Text + "','"+

brief_description.Text + "','"+ rules.Text + "','"+ pending.Text + "','"+ under_action.Text +

"')");}

privatevoidgroupBox1_Enter(objectsender, EventArgse){

}

}}

Delete Traing File

usingSystem;

usingSystem.Collections.Generic;usingSystem.Linq;

usingSystem.Text;



108/127




usingSystem.Data;


namespaceFDA_EHRM{publicpartialclassdeletetrningfile: FDA_EHRM.MainForm

{

Connectionconc = newConnection();publicSqlConnectionMyConnection = null;

publicSqlCommandMyCommand = null;

publicSqlDataAdapterMyAdapter = null;

publicDataSetMyDataset = newDataSet();privateinti = 0;

publicdeletetrningfile()

{ InitializeComponent();

}



stringConString = "Data source=ZAHID-HAMEED-HP; initial catalog=FDA_db;Integrated Security= SSPI";



MyAdapter = newSqlDataAdapter("selectFile_no,Record_no,Date_time,CNIC,Name,Starting_date,Ending_date,Subject,Training_given_b

y,Department,Venue from admin_training_tb where CNIC='"+ cnic.Text + "' ", MyConnection);

SqlCommandBuilderbuilder = newSqlCommandBuilder(MyAdapter);MyDataset = newDataSet();

MyAdapter.Fill(MyDataset, "admin_training_tb");

dataGridView1.DataSource = MyDataset.Tables["admin_training_tb"];if(MyDataset.Tables[0].Rows.Count > 0)

{

i = 0;

File_no.Text = MyDataset.Tables[0].Rows[i]["File_no"].ToString();rec_no.Text = MyDataset.Tables[0].Rows[i]["Record_no"].ToString();

datetime.Text= MyDataset.Tables[0].Rows[i]["Date_time"].ToString();

cnic.Text = MyDataset.Tables[0].Rows[i]["CNIC"].ToString();

name.Text = MyDataset.Tables[0].Rows[i]["Name"].ToString();starting_date.Text = MyDataset.Tables[0].Rows[i]["Starting_date"].ToString();

Ending_date.Text = MyDataset.Tables[0].Rows[i]["Ending_date"].ToString();

Subject.Text = MyDataset.Tables[0].Rows[i]["Subject"].ToString();given_by.Text = MyDataset.Tables[0].Rows[i]["Training_given_by"].ToString()

wasa project

Documents