ACKNOWLEDGEMENT

First, I bow my head in reverence to The God Almighty for keeping me sound and healthy for the successful completion of my project. I thank my parents who always shower their blessings upon me and support me through all the endeavors that I indulge in. The success accomplished in this project would not have been possible without the timely help and guidance rendered by many people surrounding me to whom I feel obliged and grateful. I wish to express my sincere and heartfelt gratitude to the following personalities. I express my sincere thanks to our principal Dr.Vargheese John: M.A, M.Phil, and Ph.D, for permitting me to undertake this project as part of the curriculum and our Head of the Department Prof.N.Geethakumari, M.Sc, M.Phil, for giving me the opportunity and encouragement to do this project. I express my deep sense of gratitude to our course co-ordinator, Dr.K.K.Leelamma, M.Sc, Ph.D, for the concern and attention she showed at all stages of the project. I extend my profound gratitude sincere love to my internal guide, Ms.Lince Rachael Varghese, MCA, for evincing keen interest in my project and for the guidance and support she offered through out the project. I am also grateful to Mrs. Ambika for allowing me to carry out my project work in FACT Udyogamandal.I take this opportunity to thank Mr. Sunil who gave me a proper guidance to my project work. I express my heartfelt thanks to Mr.Pramod, for his help and guidance throughout the project. I also thank all my friends and staff members at the college, who have helped me to complete this project, for their consistent support and encouragement. Ms.Binitha Baby.

SYNOPSIS

SYNOPSIS
The project family pension payment system is done for FACT welfare department, which is in charge of family pension payment system. According to this project pension is given to employees spouse or his dependent while, the employee dies on his service. A wed based computerized environment is provided by this project. Project tightly wrapped based on activities involved-employees details, dependent details, bank details, pension code details, payment slip header details. The entire system 2 basic levels employees level and dependents level. From the employees level it is a system which contain information about particular employee. From dependents level it is a system to keep details of a particular dependent according to specified employee. The system has been developing for getting pension to each dependent of specified employee in the field. Here we can enter or retrieve data about the employee, his dependent, his pension amount, his death date, pension date, pension payment to his dependent. The entire project consist of 6 modules 1: Employee details-As the name implies, it covers details of the employee mainly name of the employee, his pension code, date of death, retirement date. 2: Dependent details-It covers the details of the dependent mainly dependent name, dependent address, bank code, account number. 3: Bank master-In this module bank master contains details about the bank. 4: Pension code master-In this module it contains pension code, pension to his retirement date and pension after his retirement date. 5: Pension payment slip details-This module contains the amount of pension, date from pension is given, date to one specified and total amount.

6: Pension payment slip header-This module contains the slip code month, year showing from what period pension is given to the dependent

CONTENTS
1. INTRODUCTION & OBJECTIVE 2. SYSTEM ANALYSIS
2.1. 2. 2 2.3 2.4 2.5 IDENTIFICATION OF NEEDS

LIMITATIONS OF EXISTING SYSTEM PROPOSED SYSTEM PRELIMINARY INVESTIGATION FEASIBILITY STUDY

2.5.1. ECONOMIC FEASIBILITY 2.5.2 TECHNICAL FEASIBILTY 2.5.3. BEHAVIORAL FEASIBILITY

2.6 REQUIREMENT SPECIFICATION

2.6.1. 2.6.2. 2.6.3. 2.6.4. 2.6.5. 2.6.6. SYSTEM CONFIGURATION SOFTWARE SPECIFICATION HARDWARE SPECIFICATION THE .NET FRAMEWORK MS SQL SERVER 2000 C#.NET

2.7 DATA FLOW DIAGRAMS

3. SYSTEM DESIGN
3.1. 3.2. 3.3. 3.4. 3.5. 3.6. LOGICAL DESIGN PHYSICAL DESIGN INPUT DESIGN OUTPUT DESIGN DATABASE DESIGN FORM DESIGN

4. SYSTEM DEVELOPMENT
4.1. CODING 4.1.1. 4.1.2. 4.1.3. 4.1.4. 4.1.5. PROJECT CODING COMMENTS AND DESCRIPTION ERROR HANDLING CODE EFFICIENCY VALIDATION CHECKS

5. SYSTEM TESTING
5.1. TESTING PROCESS
5.1.1. UNIT TESTING 5.1.2. INTEGRATION TESTING 5.1.3. VALIDATION TESTING

5.2. TESTING METHODS

5.2.1. WHITE BOX TESTING 5.2.2. BLACK BOX TESTING

6. IMPLEMENTATION 7. CONCLUSION 8. BIBILIOGRAPHY 9. APPENDIX

CHAPTER-1: INTRODUCTION

1.INTRODUCTION & OBJECTIVE

Family pension payment system is a web based application for providing pension to the employees dependent, while the employee dies on his service. This project is being developed for fertilizers and chemicals Travancore limited commonly known as FACT. The Fertilizers and Chemicals Travancore Ltd, popularly known as FACT, is a leading producer of chemical fertilizers in the public sector. The company came into existence, as early as in 1944, with the setting up of the first large scale Nitrogenous factory in the country, at Udyogamandal. FACT has three manufacturing divisions, the Udyogamandal Division and the Cochin Division for producing fertilizers and Petrochemical Division for producing Caprolactum. It has also made a successful diversification into engineering fabrication by setting up the FACT engineering works (FEW). The marketing division at Udyogamandal handles the distribution of fertilizers, supported by a network of Area offices, Regional offices and Deports. The Head office and the corporate office of FACT are at Udyogamandal. FACTs two fertilizer manufacturing divisions at Udyogamandal and Cochin together have, so far produced and distribute millions of tones of fertilizer Nutrients, which helped the farmers to produce over 50 million tones of food grains Computer is an evitable part of our life. The project family pension payment system can be applied for all government companies. Every government companies give pension to their employee when retire from the service. As well as Government Issue pension to their dependence when dies on his service or give job to their dependence, when dependence is qualified. So this project is important to government companies. Through this project we can maintain pension calculation easily and accurately.

This project is developed for giving pension payment for employees dependent when the employee dies on his service. Using this project we can store, retrieve, delete, update employees and dependence details and also view pension payment dates. This project has been done in ASP.NET as front end using C# as script and SQL server 2000 as backend on the Windows 2000 Server platform.

CHAPTER-2: SYSTEM ANALYSIS

10

2. SYSTEM ANALYSIS
Analysis is the detailed study of various operations performed by a system and their relationships within and the outside the system. System analysis involves an analyzing the present information and includes introductory investigations, details investigations and including investigation. System analysis is the process of gathering and interpreting facts, diagnosing problems and using the information to recommend improvement to the system. In brief analysis specifies what the system should do. It is a management technique that heads in designing a new system or improving an existing system. To achieve these things someone must analyze the existing system and articulate the need for information and someone must conceive the means of satisfying the need.

2.1 IDENTIFICATION OF NEEDS

Identification of need is the process of identifying that there is a decision to be made. This is the first step in the system analysis process. Decisions can usually de identified by examining and analyzing existing data, presumably from the transactions and management reporting subsystems specifically, decision support systems provide managers with powerful tools to look at the data in new ways. Need identification is the simplest level of decision support. We need change over to new system. A comparison of the Existing and proposed system as to whether the system caters to the need of the user was made and a decision arrived at to go for the new computerized system.
2.2

LIMITATONS OF THE EXISTING SYSTEM

In FACT pension activities are not computerized now. So the system is a manual one. This leads to an inefficient working of department and also delay. For a complete sequential ordering, a computerized wed environment is needed. Since the entire system is a manual operation it is difficult to get the analysis of data.

11

2.3. PROPOSED SYSTEM

The proposed system includes employee details, dependent details, bank details, pension code master, pension payment slip details and pension payment slip header. The project mainly focused on pension management. The major application in this project is that easy storage and retrieval. The proposed system has the following advantages over the present system. They are time saving, easy calculation of pension, accurate.
2.4

PRELIMINARY INVESTIGATION
The first step in the system development life cycle is the preliminary

investigation to determine the feasibility of the system. The purpose of this investigation is to evaluate project requests. When that request is made, the first system activity, the preliminary investigation begins. It is not a design study nor does it include the collection of details to describe the business system in all respect. A preliminary investigation is done in FACT and got an information that existing system taking a lot of delay. So the company needs a web based computerized environment for collecting details and also providing pension to the employee dependent while the employee dies on his service

2.5

FEASIBILITY STUDY
The process followed in making this determination is called a feasibility

evaluation. This type of evaluation determines, if a project can and should be taken considered very carefully during the feasibility .It is the part of system design process. The main objective of this study is to determine whether the proposed system is feasible or not. Mainly, there are 3 types of feasibility study to which the proposed system is subjected as described below. The key considerations involved in the feasibility study is

12

 Economical feasibility Technical feasibility Behavioral feasibility The proposed system must be evaluated from a technical viewpoint first and if technical feasibility there impact on the organization must be assessed if compatible behavioral system can be devised. Then they must be tested for economical feasibility.

2.5.1 Technical Feasibility:

The assessment of technical feasibility must be based on an outline design of system requirements in terms of input, output, files, database, programs and procedures. This can be qualified in terms of volumes of data, trends, frequency of updating, cycles of activities etc. in order to give an introduction of technical system. . This is concerned with specifying equipment and software that will successfully satisfy the user requirements. At this feasibility stage different configurations that satisfy the user requirements are reviewed and selected a feasible on Through this project all the requirements such as the databases, input, output, programs and procedures are technically feasible.

2.5.2 Economical Feasibility:

Justification of any capital outlay is that, it will reduce expenditure or improve the quality of services and goods, which in turn may be expected to provide increased profits. The technique of cost benefit analysis is often used a basis for assessing economic feasibility. In this project dependent gets the pension. Thereby leads profit to the company. That we say economically feasible.

13

2.5.3 Behavioral Feasibility:

People are inherently resisted to change and computers have been known to facilitate change. Since the new proposed system is nothing to do with the ordinary customers and worker resistance to the system is very much less. On the other hand the user of the system are accessing the system through Internet and they are computer literate, so resistance from that side is also very less. People are difficult to afford the changes made by the system. But this proposed system must satisfy the needs of the user. So the user can afford the changes made by the new system.

2.6 REQUIREMENT SPECIFICATION

The SRS provides an organized way to collect all software requirements surrounding a project into one document

2.6.1. SYSTEM CONFIGURATION

There are many aspects of system configuration that should be considered. You need to think about how much of the load the server needs to be able to handle. Microsofts recommended minimum configuration is the just the bare minimum that the system will be installed on.

2.6.2 HARDWARE REQUIREMENTS:

In order to implement a new system the choice of a processor with maximum possible speed is made. There should be sufficient memory to store data and software tools for efficient processing. Processor System Memory Cache Memory Hard Disk Capacity CD ROM Drive Monitor : : : : : : Pentium III or Above. 256 Mb Recommended. 512 KB. 40 GB or Above. 52 X SVGA Color.

14

Floppy Disk Drive Mouse Modem

: : :

1.44 MB. Two Button Mouse Roller Mouse Recommended Any Modem

2.6.3 SOFTWARE SPECIFICATION

Front End Back End Server Operating System : : ASP.Net, C# : SQL Server 2000 Windows 98 / Me / 2000 / XP / 2003

2.6.4. THE .NET FRAMEWORK

The .NET framework is a multi-language environment for building, deploying and running XML web services and applications. It consists of two main parts.

COMMON LANGUAGE RUNTIME

Despite its name, the runtime actually has a role in both a components runtime and development time experiences. While the component is running, the runtime is responsible for managing a memory allocation, starting up and stopping threads and processes, and enforcing security policy, as well as satisfying any dependencies that the component might have on other components. Base classes provide standard functionalities such as input/output, string manipulation, security management, network communications, thread management, text management and user interface design features.

UNIFIED PROGRAMMING CLASSES

The framework provides developers with a unified, object oriented, hierarchical and extensible set of class libraries. Currently, C++ developers use the Microsoft foundation classes and Java developers use the Windows foundation classes. All programming languages, from JScript to C++ have similar access to the framework and developers are free to choose the language that they want to use.

15

ADVANTAGES OF ASP.NET
Enhance performance World-class tool support Power and Flexibility Simplicity Manageability Scalability and Availability Customizability and Extensibility Security Language support Language compatibility

2.6.5. MS SQL SERVER 2000

SQL Server 2000 exceeds dependability requirements and provides innovative capabilities that increase employee effectiveness, integrate heterogeneous IT ecosystems, and maximize capital and operating budgets. SQL Server 200 provides the enterprise data management platform the organization needs to adapt quickly in a fast-changing environment. With the lowest implementation and maintenance cost in the industry, SQL Server 2000 delivers rapid return on data management. SQL Server 2000 supports the rapid development of enterprise-class business applications. Because of scalability, speed, and performance, SQL Server 2000 is a fully enterprise-class data database product, providing core support for Extensible Markup Language (XML) and Internet queries.

2.6.6. C#.NET
C# was created to be the programming language best suited for writing enterprise applications for .NET. C# combines the high productivity of Microsoft Visual Basic with the raw power of C++. It is a simple, object-oriented, and typesafe programming language that is based on the C and C++ family of languages. C# was developed by Microsoft. It is simpler as VB. Besides that, C# is a Java like language for web programming and it has some good features of Delphi too. Microsoft says, that C# is the best language to develop its .NET Framework applications.

16

FEATURES:

Takes full advantage of the .NET platform The most efficient compiler in the .NET family A modern replacement for C++ Enhance developer productivity and increases safety, by enforcing script type checking.

2.7 DATA FLOW DIAGRAMS (DFD)

A Data Flow Diagram (DFD) or a Bubble chart is a network that describes the flow of data and processes that change, or transform data

17

through out the system. This network is constructed by using a set of symbols that do not imply a physical implementation. It is a graphical tool for structured analysis of system requirements. DFD models a system by using external entities from which data flows to a process, which transfer the data and creates, output-data-flows which go to other external entities or files. There are various symbols used in a Data Flow Diagram. Bubbles represent the processes. Named arrows indicate data flow. External entities are represented by rectangles. They either supply or consume data. Entities that supply data are called data source and those consumes are called sinks. Data are stored in a data store by a process in the system. It is represented by open-ended rectangle.

SYMBOLS USED

Represents data source or destination

Represents flow of data

Represents process

Represents data store

18

CONTEXT LEVEL DIAGRAM

Username Admin Password Family pension payment system

Pension amount User Pension period, Employee details

19

Level-2 DFD

login details Admin 1. login process

login_id

login_form password

20

Level-1 DFD

Username 1. Login Process Password

2. Employee Report

Employee details User

Admin

3. Pension Calculations

Pension details

21

Level-2 DFD
Dependent details 1.Employe e Report Dependent details bankdetails Bankmaster Employee details 2.Pension Calculations Pensioncode Employee details

Admin

Login Process

Pension amt

Pension payment data Pension code details Pension payment slip details Pension period Pension payment slip header

22

CHAPTER-3: SYSTEM DESIGN

23

3. SYSTEM DESIGN
Design is the phase that indicates the final system. It is the solution, the translation of requirements into ways of meeting them. In this phase the following elements were designed namely, dataflow, data stores, processes, procedures. Firstly the logical design was done where the outputs, inputs and databases and procedures was formulated in a manner that meet the project requirements. After logical design physical construction of the system is done. After analyzing the various functions involved in the system the database, tables and dictionary was designed. Care is taken for the field name to be in self explanatory form. Unnecessary fields are avoided so as not to affect the storage of the system. Care must be taken to design the input screen in the most user friendly way so as to help even the novice users make entries approximately in the right place All input screens in the system are user friendly. The sizes of all the screens are standardized. The importance of the software design can be stated with a single word quality. Design is a place where quality is fostered in software development. Design is the only way where requirements are actually translated into a finished software product or system.

3.1 INPUT DESIGN

Input design is the process of coverting the useroriginated input to a computer based format. The design decision for handling input specify how data are accepted for computer processing. Input design is a part of overall system design that needs careful attention. The collection of input data is considerd to be the most expensive part of the system design.Since the inputs have to be planned in such a way so as to get the relevant information,extreme care is taken to obtain the pertinent information. If the data going into the system is incorrect then the processing and outputs will

24

magnify these errors. The goal of designing input data is to make data entry as easy, logical and free from erors as possible. The following are the objectives of input design: To produce a cost effective method of input. To make the input forms understandable to the end users. To ensure the validation of data inputs. The nature of input data is determined partially during logical system deign.However the nature of inputs is made more explicit during the physical design. The impact of inputs on the system is also determined. Effort has been made to ensure that input data remains accurate from the stage at which it is recorded and documented to the stage at which it is accepted by the computer.Validation procedures are also present to detect errors in data input, which is beyond control procedures. Validation procedures are designed to check each record, data item or field against certain criteria. 3.2 OUTPUT DESIGN The output design phase of the system design is concerned with the conveyance of information to the end users in a user friendly manneer. The output design should be efficient, intelligible so that the systems relationship with the end user is improved and thereby enhancing the process of decision making.
The output design is an ongoing activity almost from the beginning of the project, and follows the principles of form design. Efficient and well-defined output design improves the relation of the system and the user, thus facilitating decision making. The primary considerations in the design of the output are the requirement of the information and the objectives of the end users.The output design should be efficient, intelligible so that system relationship with the end user is improved and theyre by enhancing the process of decision making. Points to be noted while designing output screen:

25

Design output to fit the user. Deliver the appropriate quantity of output. Assure that output is where it is needed. Provide output on time

26

3.3 DATABASE DESIGN

Database design is required to manage the large bodies of information. The management of data involves both the definition of structure of the storage of information and provisions of mechanism for the manipulation of information. In addition to the database system must provide for the safety of information handled, despite the system crashes due to attempts art unauthorized access. For developing an efficient database, we will have to fulfill certain conditions such as: Control redundancy. Ease of use. Data independence. Accuracy and integrity. Avoiding inordinate delays. Recovery from failure. Privacy and security Performance. There are 6 major steps in design process. The first 5 steps are usually done on paper and finally the design is implemented. Identify the table and relationships. Identify the data that is needed for each table and relationship. Resolve the relationship. Verify the design. Implement the design.

NORMALIZATION
Normalization is a technique that is more applicable to record based data models. Each of the process can be carried out independently to arrive at

27

normalized tables. Normalization refines the data structure and data are group in simple way as possible. So later changes can be bring about the least impact on database structure and eliminates data redundancy.

DATA INTEGRITY
Data integrity refers to the procedure that ensures correctness of the data entered in the database. Functions have been provided in the software, which check data while being entered. Integrity problems are occurred due to hardware or software malfunctions such as power failure and disk crashes. Side effect from the program development may also be the reason.

DATA CONSISTENCY
Problem with data consistency occur when adding records without first checking for records with same key or deleting records without deleting other related records. Likewise the software is coded such that primary keys cant be duplicated. For developing an efficient database, we have to fulfill certain conditions such as Control redundancy Ease of use Data independence Privacy and security Performance For achieving the above criterias we have to make use of various features that are available with DBMS such as: Enforcing integrity constraints to ensure data integrity and to reduce data inconsistency.

Recovery from failures using backup facility.

28

Table name: Employee details

Table name Pen_code Pener_code Emp_name Death_date

Datatype Bigint Bigint Varchar Datetime

Length 8 8 50 10

Description Pension code Pensioner code Employee name Date of death

Constraints Primary key . .. ..

Rtd_date Cre_date Cre_by Modi_date Modi_by

Datetime Datetime Varchar Datetime Varchar

10 10 50 10 50

Date of retirement Created date Created by

. .. ..

Modified date Modified by ..

29

Table Name: Dependent Details

Field name Pen_code

datatype Bigint

Length 8

Description Pension code

Constraints Primary key .

Dep_name Dep_addr1 Dep_addr2 Phno Pincode Bank_code Acc_no

Varchar Bigint Bigint Numeric Numeric Bigint Varchar

50 8 8 9 9 8 50

Dependent name Permanent address of dependent Temporary address of the dependent Contact number of the dependent Pincode Bank code Account number

Foreign key

Cre_date Cre_by Modi_date Modi_by

Datetime Varchar Datetime Varchar

10 50 10 50

Created date Created by Modified date Modified by

30

Table name:login_form

field name Login_id password

datatype Bigint varchar

length 8 20

description Login id password

constraints Primary key .

Table name:Bank details

Field name Bank_code Bank_name Bank_addr1 Bank_addr2 phno datatype Bigint Varchar Varchar Varchar numeric length 8 50 50 50 9 Description Bank identification Code Name of the bank Address of the main branch Address of the sub branch Contact phone number of the bank Constraints Primary key . . ..

31

Field name Pen_code

datatype length description constraints Bigint 8 Pension code Primary key

Pen_amt_before Variant

Pension amount before retirement Pension amount after retirement 50 Name of the person created Date of creation

Pen_amt_after

Variant

Cre_by

Varchar

Table name:pension code details

Cre_date

datetime 10

..

32

Table name:pension payment slip details

Field name Pen_code Pen_from_date Total Cre_by Cre_date

datatype Datetime Datetime Bigint Varchar Datetime

length 10 10 8 50 10

description Pension code Date from which pension given Total amount given Name of the person Created Date of creation

Constraints Primary key .. .

33

 Modi_by Modi_date Varchar datetime 50 10 Modified by Modified date

Table name: pensionslipheader

Field name
Pen_code Pen_month Year

datatype
Bigint Bigint Bigint

length
8 8 8

description
Pension code Month on which pension is given Year showing how long pension

Constraints
Primary key .. ..

34

Cre_by Cre_date Modi_by Modi_date

Varchar Datetime Varchar Datetime

50 10 50 10

is given Name of the person created Date of creation Name of the person modified Date of modification

.. .. .. ..

CHAPTER-4:

35

SYSTEM DEVELOPMENT

4.1. CODING
4.1.1. COMPLETE PROJECT CODING
The project code has been kept secure and therefore the company does not allow publishing of the code.

4.1.2. COMMENTS AND DESCRIPTION

Comments and description are used in coding to improve the understandability of the code and also to improve maintanenance. Since a website is a mix of HTML tags and server side and client side codes the pages would be complicated and difficult to understand. So to improve readability proper comments are given within each page and each module.

36

4.1.3. ERROR HANDLING

A System should also perform proper error handling. Since the proposed system is web based all exceptions are thrown in the web server. These exceptions need to be tracked properly and have to be managed. The exceptions thrown will be written to the event log of the machine so that it will be available in the web server event log which can be checked by the developers.

4.1.4. CODE EFFICIENCY

Code efficiency aims at improving the execution by eliminating redundancies and by rearranging computations in the program without affecting the meaning. The basis of code efficiency lies in the structure of the program and the manner in which the data is defined and used in the program.

4.1.5. VALIDATION CHECKS

Validation check involves the process of checking the input data to ensure that it is complete, accurate and reasonable. Although it would not be possible to guarantee that only valid data are entered into a computer, the system implements many validation checks.

Data validation This guarantees that every data entered into the system is correct and accurate. Several types of data validation are there. Some of them are: Data Type Check Each input data item is checked to ensure that it matches with the data type of the table column in which it will be stored. Field Length Check The number of characters in an input field is checked to ensure that it does not exceed the limit fixed for the field. Range Check

37

An input numerical data item as well as the calculated field is checked to ensure that its value falls within the range supported by the corresponding table field.

CHAPTER-5:

SYSTEM TESTING

38

TESTING AND IMPLEMENTATION

System testing is the stage of implementation, which is aimed at ensuring that the system works accurately and efficiently before live operation commences. Testing is vital to the success of the system. System testing makes a logical assumption that if all the parts of the system are correct, the goal will be successfully achieved. The candidate system is subject to a variety of tests. A series of tests are performed for the proposed system before the system is ready for user acceptance testing. The testing steps are: Unit testing Integration testing Validation testing Output testing User acceptance testing

UNIT TESTING
Unit testing focuses verification efforts on the smallest unit of software design, the module. This is also known as module testing .The modules are tested separately. This testing is carried out during programming stage itself. In this testing step, each module is found to be working satisfactorily as regard to the expected output from the module.

INTEGRATION TESTING
Data can be lost across an interface; one module can have an adverse effect on others; sub-functions when combined may not produce the desired major functions; integration testing is a systematic testing for constructing the program structure. While at the same time conducting to uncover errors associated within the interface? The objective is to take unit tested modules and to combine them and test it as a whole. Here correction is difficult because the vast expenses of the

39

entire program complicate the isolation of causes. This is the integration-testing step; all the errors encountered are corrected for the next testing step.

VALIDATION TESTING
Verification testing runs the system in a simulated environment using simulated data. This simulated test is sometimes called alpha testing. This simulated test is primarily looking for errors and monitions regarding end user and decisions design specifications hat where specified in the earlier phases but not fulfilled during construction. Validation refers to the process of using software in a live environment in order to find errors. The feedback from the validation phase generally produces changes in the software to deal with errors and failures that are uncovered. Than a set of user sites is selected that puts the system in to use on a live basis. They are called beta tests. The beta test suits use the system in day to day activities. They process live transactions and produce normal system output. The system is live in every sense of the word; except that the users are aware they are using a system that can fail. But the transactions that are entered and persons using the system are real. Validation may continue for several months. During the course of validating the system, failure may occur and the software will be changed. Continued use may produce additional failures and need for still more changes. OUTPUT TESTING After performing the validation, the next step is output testing of the proposed system, since no system could be useful if it does not produce the required output in the specified format. Asking the users about the format required by them tests the output generated or displayed by the system under consideration. Hence the output format is considered in two ways-one is on screen and another in printed format.

40

USER ACCEPTANCE TESTING User acceptance of a system is the key factor for the success of any system. The system under consideration is tested for the user acceptance by constantly keeping in touch with the prospective system users at the time of developing and making changes whenever required. This is done in regard to the following point: Input Screen Design Output screen Design Online message to guide the user Format of reports and other outputs An acceptance test has the objective of selling the user on the validity and reliability of the system .it verifies that the systems procedures operate to system specifications and that the integrity of important data is maintained. Performance of an acceptance test is actually the users show. User motivation is very important for the successful performance of the system. After that a comprehensive test report is prepared. This report shows the systems tolerance, Performance range, error rate and accuracy.

41

CHAPTER-6: SYSTEM IMPLEMENTATION

42

SYSTEM IMPLEMENTATION
Implementation is the stage in the project where the theoretical design is turned into a working system and is giving confidence on the new system for the users that it will work efficiently and effectively. It involves careful planning, investigation of the current and its constraints on implementation, design of methods to achieve the change over, an evaluation, of change over methods. Apart from planning major task of preparing the implementations are education are training of users. The more complex system being implemented, the more involved will be the system analysis and the design effort required just for implementation. An implementation coordinating committee based on policies of individual organization has been appointed. The implementation process begins with preparing a plan for the implementation of the system. According to this plan, the activities are to be carried out, discussions made regarding the equipment and resources and the additional equipment has to be acquired to implement the new system. Implementation is the final and important phase. The most critical stage in achieving a successful new system is giving the users confidence that the new system will work and be effective. The system can be implemented only after through testing is done and if it found to working according to the specification. This method also offers the greatest security since the old system can take over if the errors are found or inability to handle certain type of transactions while using the new system. At the beginning of the development phase a preliminary implementation plan is created to schedule and manage the many different activities that must be integrated into plan. The implementation plan is updated throughout the development phase, culminating in a changeover plan for the operation phase. The major elements of implementation plan are test plan training plan, equipment installation plan and a conversion plan.

43

There are three types of implementation: Implementation of a computer system to replace a manual system. Implementation of a new computer system to replace an existing one. Implementation of a modified application to replace an existing one, using the same computer. The type used for this software is to replace and manual system type. Here exchanges the manual works whole to the system

44

CHAPTER-7:

CONCLUSION

45

CONCLUSION
This project was successfully completed within the time span allotted. The project FAMILY PENSION PAYMENT SYSTEM has been developed in ASP.NET. All the modules are tested separately and put together to form the main system. Finally the system is tested with real data and everything worked successfully. Thus the system has fulfilled the entire objective identified. The system had been developed in an attractive dialogs fashion. So user with minimum knowledge about computers can also operate the system easily. It will make easy interactions between users and store. The speed and accuracy are maintained in proper way.

46

CHAPTER-8 BIBLIOGRAPHY

47

BIBLIOGRAPHY

Matthew Mac Donald: The Complete Reference ASP.NET

Kalen Delaney: Inside MS SQL Server 2000 James A. Sam : Database Management System Roger S. Pressman : "Software Engineering James Hoffman: Introduction to Structured Query Language,4th Edition John Stubbe, Marvin Gore: Elements of System Analysis Microsoft ASP_NET QuickStart Tutorial

48

APPENDICES

49

SAMPLES FORMS

50

HOME PAGE

51

LOGIN FORM

52

EMPLOYEE DETAILS

53

DEPENDENT DETAILS

54

BANK DETAILS

55

PENSION CODE DETAILS

56

PENSION PAYEMENT SLIP DETAILS

57

PENSION SLIP HEADER

58

59