IEE Project Report Format

ABSTRACT

Every individual in a society who possess certain earnings though several sources have to remit a certain percentage to the government treasury .This income is basically known as the income tax which aims at nations prosperity .Each government will issue tax according to the income tax act passed by the government.

Income of an individual is earned over a period of time and the assessment/determination of tax is a regular flow of revenue for the government, here we propose” tax planning worksheet” which make possible for every individual to plan their savings.

With this project, we could be able to resolve the problems during the calculation of the income tax of a particular individual. Tax planning involves conceiving of and implementing various strategies in order to minimize the amount of taxes paid for a given period. In this way tax planning can be a source of working capital

Planning ones income may/may not be a difficult question to answer but tax planning has been something which people may have found out to be very difficult. There are many parameters that we need to take into consideration while planning for our tax, as the benefit is going to be received by the government. In our project we help the individuals to calculate their total income tax for a particular assessment year. And in order to reduce the tax rate ,proper planning is what is required. We have to compare the advantages of several tax saving schemas and depending upon our age, social liabilities, tax slabs and personal preferences, decide upon right mix of investments, can reduce our tax liability to zero or the minimum possible.

Our project consisted of various chapters that describe our whole project .There are mainly six chapters for our project .In the first chapter ,requirement analysis and specification provides the details for how the user interviews are conducted. DFD, ER, context analysis diagrams are designed and finally the detailed specific requirement specification document also. The chapter includes the narration of proposed system and its advantages over existing system .The chapter deals with the proposed system ,problems encountered in the existing system .The system requirement specification which deals with the product perspective product functions are also included in this chapter.

The second chapter of the project is design analysis and specification.The Software Design Document is a document to provide documentation which will be used to aid in software development by providing the details for how the software should be built. Within the Software Design Document are narrative and graphical documentation of the software design for the project Identifying tax planning worksheet

This document is a high level design document (HLDD) of the system. The intended audiences for this document are the individuals, who want to do their tax calculation and can plan their savings for their lifetime. As described software is implemented using C#. Knowledge in the specific fields of dot net will be much helpful for the reader to understand the contents easily.

In the design chapter, we have completed the design of our process and the database. In the database design we have designed the tables which describe the fields, constraints and the descriptions. In the process design, various screenshots related to our project have been made.

The third chapter of the project is coding.The document coding provides the details on different modules of source codes which are developed by the programmer and the details about the standard library functions used for the development of indented software. This chapter describes about the tools and technologies used for coding in great detail.

The fourth chapter of our project is testing.The chapter testing describes various testing methodologies which are adapted and detailed view of test data’s within each database. During testing of a program to be tested is executed with a set of test data and the output of the program for test data is evaluated.

The fifth chapter deals with implementation.Implementation is a process of converting a new system into an operational one. The designed system is converted into an operational one using a suitable programming language. Implementation includes all those activities that take place to convert an old system into a new one. Proper implementation is necessary to provide a reliable system to meet organizational requirement

The sixth chapter deals with the operations manual.The operations manual provides user-friendly input and output forms that have been designed with interactive dialogue. It enables the end users to insert details very easily through corresponding interface forms. In this section we deals with various screenshots of our project.

TAX PLANNING WORKSHEET

MAIN PROJECT REPORT

Submitted in partial fulfilment of the requirement for the award of the degree

of Bachelor of Technology in Computer Science and Engineering

of the University of Calicut

Submitted by :

DEJI JOSE

KAVYA P N

RAJALAKSHMI P B

RESHMA RADHAKRISHNAN

STEFY JOHN

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

KMCT COLLEGE OF ENGINEERING

MANASSERY (P.O), KOZHIKODE

KERALA

2011

K.M.C.T COLLEGE OF ENGINEERING

CALICUT

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CERTIFICATE

This is to certify that this Main Project Report titled “TAX PLANNING WORKSHEET” is the bonafide record of the work done by DEJI JOSE(CTAHECS016), KAVYA P N (CTAHECS025), RAJALAKSHMI P B(CTAHECS034), RESHMA RADHAKRISHNAN (CTAHECS039) and STEFY JOHN (CTAHECS055) of Eighth semester, Computer Science and Engineering, towards the partial fulfilment of the requirements for the award of the Degree of Bachelor of Technology by the University of Calicut.

PROJECT GUIDE HEAD OF THE DEPARTMENT

Place:

Date :

ACKNOWLEDGEMENT

We would like to express our sincere thanks to the director Dr.V.B Panicker of KMCT College of Engineering, Calicut

We express our deepest sense of gratitude to our Dean Mr. Pratap G Nair and our Head of the Department of Computer Science and Engineering Mrs. Daphna Chacko for their valuable advice and guidance.

With immense pleasure and heartiest gratitude, we express sincere thanks to Mrs. Daphna Chacko, HOD of Computer Science and Engineering for his valuable suggestions and guidance.

I also thank our staff members and friends for their kind hearted support and encouragement.

Above all, we thank the almighty for enabling us to be what we are.

STEFY JOHN

CHAPTER 1

REQUIREMENT ANALYSIS

1.1 Introduction

Every individual in a society who possess certain earnings through several sources have to remit a certain percentage to the government treasury .This income is basically known as the income tax which aims at nations prosperity .Each government will issue tax according to the income tax act passed by the government. Most taxes are based on the principle on the receiver of taxes has the right to assess the tax liability, demand the assessed amount from the tax payer.

Income of an individual is earned over a period of time and the assessment/determination of tax is a regular flow of revenue for the government, here we propose” tax planning worksheet” which make possible for every individual to plan their savings.

With this project, we could be able to resolve the problems during the calculation of the income tax of a particular individual. Tax planning involves conceiving of and implementing various strategies in order to minimize the amount of taxes paid for a given period. In this way tax planning can be a source of working capital.

Meaningful tax reform requires a better understanding of how taxes interact with the economy. Whether it is called an income tax,a payroll tax, a sale tax etc.All taxes are paid out of the income people earn with their labor and capital.The current tax code needlessly hamstrings the economy because marginal tax rate exceed average rate.

Planning ones income may/may not be a difficult question to answer but tax planning has been something which people may have found out to be very difficult. There are many parameters that we need to take into consideration while planning for our tax, as the benefit is going to be received by the government. In our project we help the individuals to calculate their total income tax for a particular assessment year. And in order to reduce the tax rate ,proper planning is required. We have to compare the advantages of several tax saving schemes and depending upon our age, social liabilities, tax slabs and personal preferences, decide upon right mix of investments, can reduce our tax liability to zero or the minimum possible.

This system requires only a few information about the user, which also can be easily submitted by the user and rest of the work is self generated by the system. The monthly updating of data is generated by system through calculating the issued and received quantities.

The document requirement specification provides the details for how the user interviews are conducted. DFD, ER, context analysis diagrams are designed and finally the detailed specific requirement specification document also. The chapter includes the narration of proposed system and its advantages over existing system.

1.2 Feasibility study

The feasibility report of the project holds the advantages and flexibility of the project. This is divided into three sections:

Technical Feasibility Economic Feasibility Operational Feasibility

Behavioural Feasibility

1.2.1 Economic Feasibility

A systems financial benefit must exceed the cost of developing that system. i.e. a new system being developed should be a good investment for the organization. Economic feasibility considers the following

i. The cost to conduct a full system investigation.

ii. The cost of hardware and software for the class of application.

iii. The benefits in the form of reduced cost or fewer costly errors.

iv. The cost if there is no change (i.e. the proposed system is not developed).

The proposed “INCOME TAX PLANNING WORKSHEET” is economically feasible because

The system requires very less time factors. The system will provide fast and efficient automated environment

instead

of slow and error prone manual system, thus reducing both time and man

power spent in running the system.

The system will have GUI interface and very less user-training is required

to learn it.

2. Technical Feasibility

Technological flexibility is carried out to determine whether we have the capability in term of software, hardware, personal and expertise to handle the completion of project. It centers around the existing computer system (H/W and S/W) whether it can support the addition of proposed system, if not, to what extent it can support.

The H/W and S/W required in our system are easier to install and handle. The necessary H/W configuration and software platform is already there. The system supports interactivity with the user through GUI. So our system is technically feasible.

1.2.3 Operational Feasibility

Operational feasibility determines how much effort will go in the proposed system, and in educating and training the users on the new system. Operational study strives on ensuring that the equilibrium of the organization and status in the organization are not disturbed and changes are readily accepted by the users. The proposed system is operationally

feasible because it does not require any training for the users. One can easily calculate their tax and can do planning.

1.2.4 Behavioral Feasibility

An estimate should be made of how strong a reaction the user staff is likely to have toward the development of a computerized security system. It is common knowledge that computer installations have something to do with turnover, transfer, retaining and changes in employee job status. Introduction of this software does not require any special effort to educate and train the staffs because this software is not so complicated and easy to understand.

1.3 Project plan

Our group consists of five members and we worked together according to a detailed plan to ensure quality in all aspects for assigning tasks to each member clearly.

Project name: Tax Planning worksheet Project site: Income tax office

Guide: Mrs. Daphna Chacko Submitted on: 19/05/2011

TABLE 1.1 PROJECT PLAN

Sl no Activity description Role Start date Target date

1 Topic identification All members 10/09/10 15/10/10

2 Feasibility study Reshma Kavya

20/09/10 23/10/10

3 User interview All members 25/09/10 30/10/10

4 Requirement analysis All members 01/10/10 05/10/10

5 SRS preparation Deji

Stefy

Rajalakshmi

15/10/10 25/10/10

6 Design All members 26/10/10 30/10/10

7 Coding All members 2/01/11 29/04/11

8. Testing, Implementation All members 30/04/11 15/05/11

Team members:

DejiJose

Kavya P.N

Rajalakshmi P.B

ReshmaRadhakrishnan

1.4 User interviews

In order to understand about the tax calculation, the requirement analysis had been conducted at Income Tax office, Mananchira, Calicut. A per the project start up and planning procedure, our team went there and interacted with Mrs.Vijayalakshmi(Senior Inspector ,Department of Income Tax).She had provided us with the current tax slabs and tax assessment forms and papers.

To learn more about the existing system, we had conducted an interview with Mr. Prince Joseph(Karvy solutions, near BMH Calicut).He had provided information regarding the procedures for the tax payment, various forms used for the calculation of one’s salary and tax etc. From there, we came to know that how tax is being imposed on an individual.

By describing the great process in details, we can divide the entire process into three major processes.

1. Entering user data:

The one who wish to use this software has to provide all his/her details which includes user name, password, PAN, address, e mail, date of birth etc.

2. Salary and tax calculation:

Using the data entered by the user, can calculate salary and tax.

3. Tax deduction:

In this, using the processed information tax deduction is done.

1.5 Existing system

Traditionally the tax calculation and planning process is done manually and it is very much time consuming, the operation of manual calculation is as follows the employ maintain a large indexed hard record.

Most taxes are based on the principle on the receiver of taxes has the right to assess the tax liability, demand the assessed amount from the tax payer. This has a negative effect on the tax payable by them and they eventually end up paying more taxes than they are required to.

Tax planning software provider can help your business to save some time and money when tax season come around. Several options exist for tax planning software that is easy to use and can synthesis complicated tax solution.

Tax planning software allows tax and accounting professionals to stream line tax preparation. The main functions include calculation, review, e-filing, data automation, accounting and forms automation. This software is available for local, state, federal and international levels of filing. This software is related to accounting software, financial reporting software. There are several options existing for tax planning software and is easy to use and can synthesize complicated tax solutions.

1.6 Problems encountered in the existing system

Traditionally we have been doing all the calculations manually at their own risk which may sometimes lead to logical or mathematical errors. When we want to manage our income tax returns, we should know of all the appropriate laws on taxes which can’t be just achieved by our limited knowledge.

Salaried individuals in India are not fully aware of the tax planning exercise which they rush at the end of the tax planning season and make investments to reduce their tax liability. Since all this are done manually, data redundancy will be high which leads to lower storage capacity. Since we require lot of paper works, it is very difficult to keep all the records safely and securely. Each time when the calculations are done , lot of time is required.

Major drawbacks of the system are:

Time consuming Difficult computations Logical and mathematical knowledge is necessary

1.7 New requirements

The proposed system “Tax planning worksheet “will make use of web which help the users to calculate and plan their income tax in a given time. This is also useful for storing all the details regarding the salary and other possible deductions. There is no need to enter values for each month. It is done automatically.

The added advantages of this system are:

Less usage of man power Faster processing User friendly Highly secure Automatic reports for tax deduction statement is produced

8. Proposed system

Our proposed system “tax planning worksheet” requires only less usage of the man power and provides high security to one who is using it .It is user friendly and has a better performance speed .Our software is a fully automated one in which automated reports based on the tax deductions are produced.

1.8.1 Decomposition of Proposed System

There are two main modules in this system. They are administration module and user module.

1. Administration module: In this module administrator does the tax slab updation process.

2. User module: In this user enters data and calculate salary and tax and do planning.

1.9 Requirement analysis

Requirement analysis is a process of understanding the customer needs and expectations from a proposed system or application and is a well-defined stage in software development life cycle model. This provides a software for the user who wish to calculate his/her tax, which is more reliable, user friendly and thorough interaction with the database.

Requirements are the description of how a system should behave or a description of system properties and attributes. It can alternatively be a statement of ‘what ‘an application is expected to do.

A dedicated and specialized requirement analyst is best equipped to handle the jobs. The requirement analysis function may also fall under the scope of project manager, program manager, depending on the organizational hierarchy.

1.10 Software and Hardware requirements

1.10.1 Hardware interfaces

800 MHZ Pentium3 256 MB RAM 40 GB Hard disk CD drive 40X Windows XP

Hardware configuration is that the physical components used for the developing of the project. The best hardware environment provides the developer with the best utilization of the available resources.

The importance of hardware configuration comes into scene when the project development is in its peak utilization of the system’s physical resources. It can be observed that for developing a software project, one needs a better and higher configuration of the hardware than which is needed for its actual plan.

In this case a good set of hardware resources must be present there for the smooth running of .NET environment.

2. Software interfaces

technology used is ASP 2.0 scripting language C # .net back end Oracle 10g

This is the software configuration in which the project was shaped. The programming language used, tools used, etc are described here.

11. General Description

The existing tax calculation and planning system of our country is based on manual process. It is very expensive and time consuming. This process needs more human resources, lots of paper works, data querying and updating inconvenience and huge amount of time. Our main goal is to improve the value of the existing system. By accessing the entered values we can automatically calculate the tax and salary and then the deducted tax. An automated management system combines high security of the information and flexibility of use.

1.12 Specific requirements

There should be minimum and specific requirements for our system to be active. Mainly there are two categories they are hardware as well as software complexities. The system should have a browser to the web pages.

1.12.1 Functional Requirements

Our system mainly has two modules, a user module and an administration module. Various processes involved in these two modules are:

Slab Updation

Introduction: Administrator plays a greater role in this process. This comes under the administration module.

Input: The current tax slab according to the Income Tax Act of government of India would be the input for slab updation.

Process: slab updation according to the recent Income Tax of Government of India is the main process.

Output: The updated slab can be viewed by the user.

Registration

Introduction: Here the user enters his/her personal data Input: The details of the user regarding his name, address, date of birth ,Pan,

category are the main input. Process: The user data is stored in the corresponding databases and is used in

other processes for performing the calculations. Output: The user has been registered successfully.

Salary Calculation

Introduction: This process is to calculate salary. Input: The input here is the one month details of an individual’s deductions, and

his/her other savings. Process: The informations are stored in the corresponding databases and are used

for the further procedures. Output: In this process, the salary of a particular individual is calculated and

displayed.

Tax calculation

Introduction: Used by the user for tax calculation. Input: Input here is the total salary and all deductions of a user. Process: The process involved here is the tax calculation of a particular individual

taking consideration of his/her salary, savings and deductions. Output: The final tax that has to be paid by an individual can be viewed.

1.13 Product Function

This software generates the report of deducted salary details, slab updation. Here the major product functions are:

Salary Calculation

Tax Calculation Deduct salary Produce report on deducted salary

1.14 Identification of Entities & Attributes

Table 1.2 Entities & Attributes

Entities Attributes

Employee Emp_id

Emp_pswd

F_name

M_name

L_name

Flat_no

Flat_no

Building Road

District

State

pin

emp_pan

sex

Emp_category

Tel_no

Code

Ref_no

DOB

tan

Total salary calculations For_month

Hra

Pay

Da

Iri

K_g

Sli

Gis

Lic

Fbs

Hba

Yr_frm

Yr-to

Pan

Tot1

Tot2

Deducted salary Yrfrm

Yrto

Prn

Ap

Ded

Tca

Aoi

Deducted Salary record Gsi_

Ls

Fa

Rp

Ea

Ptp

Aoi

M_claim

Expand_medi1

Expand_midi2

Loan_intrst

Donation

Contribution

Nsc

Contr

Depo

Plan

M_fund

P_fund

T_fee

H_loan

S_or_d

Mut_fund

Ppf

Bonds

Sen_citizen

P_office

Lip

Pan

Hra

Gis

Lic

Yrf

Yrt

Dte

Hba

Rdn

Slab updates Ass_yr_frm

Ass_yr_to

Tpe

Sal_frm

Sal_to

Rte

T_cal Tti

S_charge

Isp

Edu_cess

Ttp

Btp

Pan

Tan

Tir

Dte

Ded

1.15 Context Analysis Diagram (CAD)

The Context Analysis Diagram (CAD) may be used to represent the top level overviews of the existing system. The CAD is drawn to represent the state of the system during the requirement analysis phase.

The CAD shows the system as a single process represented by a circle at the center of the model. There shall always be only one system process in a CAD. The model shows entities external to the system process. The entities are representative of the existing significant objects in the current system scenario. The external entities are connected to the central process through connectors representing the information flowing into/ out of the system. CAD should be drawn with the help of latest version of the Turbo Analyst tool available with the company.

Fig 1.1 CAD

1.16 Data Flow Diagram (DFD)

As the name suggests DFD is a representation of the data flow within the system. It includes processes, data stores and external interfaces to the system. External interfaces may be treated as external entities. DFD’s can by explode to sub-processes. Any two entities/data stores must be connected to each other by some process. The processes cannot be directly connected to each other. The following are the four major components of the DFD:

Process External Entity Data Store Connector

The DFD is also known as the bubble chart. It is a simple graphical formalism that can be used to represent a system in terms of the input data to the system, various processing carried out in these data and the output data generated by the system. The main reason why this DFD technique is so popular is probably because of the facts that DFD is very simple formalism. It is simple to understand and use. A DFD model uses a very limited number of primitive symbols to represent the functions performed by a system and the data flow among these systems. Starting with a set of high-level functions that a system performance of DFD model in hierarchically it represents various sub functions. The Data Flow Diagramming technique also follows a simple a simple set of intuitive concepts and rules.

DATAFLOW DIAGRAM (DFD)

Fig 1.2 DFD

1.17 Entity-Relationship Diagram (ERD)

The Entity Relationship Diagram (also known as an ERD or E-R diagram) is a network model that describes the stored data layout of a system at a high level of abstraction. The ERD should represent the relationships between all the entities. Any two entities must be connected to each other by some relationship set and type of relationship should also be specified.

Components of an ERD

There are two major components of an ERD:

Entity:

It is defined as any object about which information is collected. It has different attributes which describe it. It should be represented by a regular box as shown below:

Relationships:

Entities are connected to one another by relationships. a relationship represents a set of connections between entities and represent by a diamond.

A relationship is a two-directional significant association.

There are three types of relationships

One-to-one relationships One-to-many relationships Many-to-many relationships

ERD:-

Fig 1.3 ERD

1.18 Conclusion

The subsection of the chapter provides an overview of proposed system design and its other functional requirements clearly and precisely.

CHAPTER 2

DESIGN SPECIFICATION

2.1 Introduction

The Software Design Document is a document to provide documentation which will be used to aid in software development by providing the details for how the software should be built. Within the Software Design Document are narrative and graphical documentation of the software design for the project identifying our project tax planning worksheet.

This document is a high level design document (HLDD) of the system. The intended audiences for this document are the individuals, who want to do their tax calculation and can plan their savings for their lifetime. As described software is implemented using C#. Knowledge in the specific fields of dot net will be much helpful for the reader to understand the contents easily.

2.1.1 Purpose

The purpose of the Software Design Document is to provide a description of the design of a system fully enough to allow for software development to proceed with an understanding of what is to be built and how it is expected to build. The Software Design Document provides information necessary to provide description of the details for the software and system to be built.

2.1.2 Scope

This Software Design Document is for a base level system which will work as a proof of concept for the use of building a quality system that provides a base level of functionality. This particular Software Design Document gives the detailed requirement specification of the design of the tax planning worksheet, which helps the developers and analysts for the further updates on the software.

2.2Database design

Our project is a data centric application. In a data centric application the design of the database is very important task. The general theme behind the database design is to handle information as a whole. A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and efficiently. The general objective is to make information access easy, quick, and inexpensive and flexible for the user. In a database environment, common data are available in which several users can use. The concept behind a database is an integrated collection of data and provides a centralized access to the data from the program. It makes possible to treat data as a separate resource. While designing the database several factors have to be considered to make the system as an efficient one. The key factor is the consideration of the data type. Proper data types have to be provided for the appropriate data. Normalization is done to the data so that the data would have internal consistency and maximum stability and minimum redundancy.

While designing database, several objectives must be considered:

Controlled Redundancy

Data Independence Accuracy and Integrity Privacy and Security Performance

The normalization process takes a relation schema through a series of tests to certify whether it satisfies a certain normal form. The process, which proceeds in a top-down fashion by evaluating each relation against the criteria for normal forms and decomposing relations as necessary, can thus be considered as relational design by analysis. There are mainly three normal forms: first, second, and third normal form. All these normal forms are based on a single analytical tool: the functional dependencies among the attributes of a relation.

Normalization of data can be considered a process of analyzing the given relation schemas based on their FDs and primary keys to achieve the desirable properties of,

Minimizing redundancy Minimizing the insertion, deletion, and update anomalies.

Unsatisfactory relation schemas that do not meet the normal form tests are decomposed into smaller relation schemas that meet the tests and hence the desirable properties.

The normal form of a relation refers to the highest normal form condition that it meets, and hence indicates the degree to which it has been normalized.

First normal form

First normal form (1NF) states that the domain of an attribute must include only atomic values and that the value of any attribute in a tuple must be a single value from the domain of that attribute. Hence, 1NF disallows relations within relations or relations as attribute values within tuples. The only attribute values permitted by 1NF are single atomic values.

Second normal form

Second normal form (2NF) is based on the concept of full functional dependency. A functional dependency is a full functional dependency if removal of any attribute does not hold the dependency any more.

A relation schema is in 2NF if every nonprime attribute in relation is fully functionally dependent on the primary key of that relation.

Third normal form

Third normal form is based on the concept of transitive dependency. A relation schema R is in 3NF if it satisfies 2NF and no nonprime attribute is transitively dependent on the primary key.

Our project is fully normalized up to second normal form where each key is fully depending on the primary key. The database of our project is designed using Oracle 10g and it comprise of 9 tables.

2.2.1 Tables

Employee login: This table contains the login details of an individual

Employee: This table contains the user details

Total Salary Calculations: This table gives the details of the total salary

calculations

Deducted Salary: This table gives the details of the deducted salary

Deducted Salary Record: This table gives the details of the deducted salary record

Slab Updates: This table provides the current slab updates

T_Cal: This table gives the tax calculations

Tables

Table.2.1 Employee login

Column name Description Data type Width Constraints

Emp_id Employee id Varchar2 10

Emp_pswd Employee password Varchar2 10

Table.2.2 Employee


F_name First name Varchar2 10

M_name Middle name Varchar2 10

L_name Last name Varchar2 10

Flat_no Flat number Varchar2 10

Building Varchar2 20

Road Varchar2 20

District Varchar2 20

State Varchar2 20

Pin Number 10

emp_pan Employee pan Varchar2 20

Sex Varchar2 10

Emp_category Employee category Varchar2 200

Tel_no Phone no: Number 20

Code Varchar2 250

Ref_no Reference no Varchar2 10

DOB Date of birth Varchar2 10

Table.2.3 Total salary calculations


For_month For month Varchar 50

Hra House rent allowance Number 10

Pay Number 10

Da Deduct allowance Number 10

Iri Number 10

K_g Number 10

Sli Number 10

Gis Number 10

Lic Number 10

Fbs Number 10

Hba Number 10

Yr_frm Year from Number 10

Yr-to Year to Number 10

Pan Permanent account no Varchar 20 Primary key

Tot1 Total Number 10

Tot2 Total Number 10

TABLE.2.4 DEDUCTED SALARY

Column name Description Data type Width constraints

Yrfrm Year from Varchar 10

Yrto year to Number 10

Prn Number 10

Ap Number 10

Ded Deduction Number 10

Tca Number 10

Tna Number 10

Aoi Any other income Number 10

Table.2.5 Deducted Salary record


Gsi_ Gross salary income Number 10

Ls Leave surrender Number 10

Fa Festival allowance Number 10

Rp Rent paid Number 10

Ea Entertainment allowance Number 10

Ptp Professional tax paid Number 10

Aoi Any other income Number 10

M_claim Medi claim Number 10

Expand_medi1 Expenditure on mental/physical treatment Number 10

Expand_midi2 Expenditure on medical treatment Number 10

Loan_intrst Loan interest Number 10

Donation Donation to charitable trusts Number 10

Contribution Number 10

Nsc Purchase of nsc VIIIissue Number 10

Contr Contribution Number 10

Depo Deposit Number 10

Plan Number 10

M_fund Mutual fund Number 10

P_fund Pension fund Number 10

T_fee Tution fee Number 10

H_loan Housing loan Number 10

S_or_d Substitution to equity shares and debentures of an eligible issue

Number 10

Mut_fund Mutual fund Number 10

Ppf Contributionto ppf account Number 10

Bonds Number 10

Sen_citizen Deposit under senior citizens saving scheme Number 10

P_office Post office Number 10

Lip Number 10

Pan Permanent account no: Varchar 10

Hra House rent allowance Number 10

Gis Number 10

Lic Number 10

Yrf Year from Number 10

Yrt Year to Number 10

Dte Date Date 10

Hba Number 10

Rdn Reduction Number 10

Table.2.6 Slab updates


Ass_yr_frm Assigned year from Number 10

Ass_yr_to Assigned year to Number 10

Tpe Type Varchar 175

Sal_frm Salary from Number 10

Sal_to Salary to Number 10

Rte Rate Number 10

Table.2.7 T_cal

column name Description Data type Width Constraints

Tti Tax on total income Float 10

S_charge Surcharge Float 10

Isp Float 10

Edu_cess Educational cess Float 10

Ttp Float 10

Btp Float 10

Pan Permanent account no: Number 10

Tir Number 10

Dte Date Number 10

Ded Deduction Number 10

2.3 Process Design

2.3.1 Input Design

In Input Design we mainly concerned about the Input Process. The data must be inputted to the system to produce the required output. The aim of making input design is to make the data entry as early as possible and free from errors. An input format should be logical and easy to understand. In the design, the user oriented inputs are converted into computer recognizable format.

The collection of data is the most expensive part of the system in terms of the equipment used, time and no. of clients involved etc. In the input design data is accepted and it can be readily for data processing or can be stored in a database for further use. The used forms used for inputs are very user friendly. Different names are associated with each data entry form item makes data entry an easy job. Each data entry contains a separate buttons for submitting the form and proper validation checking is carried out and necessary message will be presented to the user incase of improper data entry. All the design work is done in Microsoft visual studio Environment so that it is very easy to design as all the options and programming is inherent there and their code is automatically written in source code file. Any change made during the design phase is automatically reflected in source code.

2.3.2 Output design

It has been an ongoing activity from the beginning of the project. It includes the process of finalizing of the medium format and exact contents of each output to be produced by the proposed system. The primary objective in creating an output is accuracy and neatness. To refine sketches into detailed description of output, we have planned output with specific medium .The major outputs are crystal reports generated by visual studio.

Various processes included in our system are given below:

Slab Updation

Updated Slab

New slab entries

update

fig 2.1 Slab updation

Introduction: Administrator plays a greater role in this process. This comes under the administration module.

Input: The current tax slab according to the Income Tax Act of government of India would be the input for slab updation.

Process: slab updation according to the recent Income Tax of Government of India is the main process.

Output: The updated slab can be viewed by the user.

Registration

User data table

User details

Registration of

user

Fig2.2 Registration

Introduction: : Here the user enters his/her personal data . Input: The details of the user regarding his name, address, date of birth ,Pan,

category are the main input. Process: The user data is stored in the corresponding databases and is used in

other processes for performing the calculations. Output: : The user has been registered successfully .

Salary Calculation

User data table

Enter salary details

Save the salary

Details of

Particular year

Fig 2.3 Salary Calculation

Introduction: This process is to calculate salary. Input: The input here is the details of an individual’s deductions, and his/her other

savings. Process: The informations are stored in the corresponding databases and are used

for the further procedures.

Output: In this process, the salary of a particular individual is calculated and displayed.

Tax calculation

Enter salary deduction details

Tax calculation table

total tax

Fig 2.4 Tax calculation

Introduction: Used by the user for tax calculation. Input: : Input here is the total salary and all deductions of a user Process: The process involved here is the tax calculation of a particular individual

taking consideration of his/her salary, savings and deductions. Output: The final tax that has to be paid by an individual can be viewed.

2.4 Conclusion

The document contains the detailed design of database, user interfaces which include input and output design separately and finally the process decomposition also.

CHAPTER 3

CODING

1. Introduction

The document coding provides the details on different modules of source codes which are developed by the programmer and the details about the standard library functions used for the development of indented software. This chapter describes about the tools and technologies used for coding in great detail.

Tools and technologies

The ORACLE 10 G program allows us to store and retrieve data in the relational database management system. Databases consist of tables which can be manipulated by Oracle query commands. It is an industry leading database system designed for mission critical data storage and retrieval. It is responsible for accurately storing data and efficiently retrieving that data in response to user queries.

The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. To provide consistent object-oriented programming environment whether object code is stored and executed locally but Internet distributed, or executed remotely, code-execution environment that minimizes software deployment and versioning conflicts, that guarantees safe execution of code, including code created by an unknown or semi-trusted third party, that eliminates the performance problems of scripted or interpreted environments.

ASP.NET uses compiled code written in Common Language Run time languages such as Visual Basic and C#. Unlike previous versions of Active Server Pages, this version does not use interpreted scripting languages such as C# Script.

ORACLE 10 G

Its features include:

Internet Integration.

The ORACLE 10 G database engine includes integrated XML support. It also has the scalability, availability, and security features required to operate as the data storage component of the largest Web sites. The ORACLE 10 G supports features such as English Query and the Microsoft Search Service to incorporate user-friendly queries and powerful search capabilities in Web applications

Enterprise-Level Database Features.

The ORACLE 10 G database engine supports the features required to support demanding data processing environments. The database engine protects data integrity while minimizing the overhead of managing thousands of users concurrently modifying the database. ORACLE 10 G distributed queries allow you to reference data from multiple

http://ASP.NET/

sources as if it were a part of a ORACLE 10 G database, while at the same time, the distributed transaction support protects the integrity of any updates of the distributed data. Replication allows you to also maintain multiple copies of data, while ensuring that the separate copies remain synchronized. You can replicate a set of data to multiple, mobile, disconnected users, have them work autonomously, and then merge their modifications back to the publisher.

Ease of installation, deployment, and use.

ORACLE 10 G includes a set of administrative and development tools that improve upon the process of installing, deploying, managing, and using ORACLE 10 G across several sites. ORACLE 10 G also supports a standards-based programming model integrated with the Windows DNA, making the use of ORACLE Server databases and data warehouses a seamless part of building powerful and scalable systems. These features allow you to rapidly deliver ORACLE Server applications that customers can implement with a minimum of installation and administrative overhead.

Coding Methodology

Primary goal of coding phase is to translate the given design into source code in a given programming language so that the code is simple, easy to test and easy to understand and modify. The coding methodologies used are the following:

Top down implementation Structured programming

Code

Reusable codes

Reusable codes can be used in anywhere by changing the parameters according to their purpose.

1.for inserting values into the table

cl.pemp_id = TextBox1.Text;

cl.pemp_pswd = TextBox2.Text;

2.link code

Response.Redirect("Empr_Default.aspx");

3.for checking the row present in the table

DataTable dt = new DataTable();

dt = psd.sel_sal(csd).Tables[0];

if (dt.Rows.Count > 0)

4. to take the values into textbox

TextBox1.Text = dr1[0].ToString();




5.to call the procedure and content classes

CONT_SALARY_DEDUCTIONS csd = new CONT_SALARY_DEDUCTIONS();

PROV_SALARY_DEDUCTIONS psd = new PROV_SALARY_DEDUCTIONS();

6.to take the values into crystal report

OracleConnection con = new OracleConnection(@"Data Source=kmct;User ID=itax;Password=itax;Unicode=True");

OracleCommand cmd = new OracleCommand();

cmd.Connection = con;

cmd.CommandType = CommandType.StoredProcedure;

cmd.Parameters.Add("vn", OracleType.Cursor).Direction = ParameterDirection.Output;

OracleDataAdapter adp = new OracleDataAdapter();

adp.SelectCommand = cmd;

cmd.CommandText = "SEL_TOTAL_SAL1";

OracleParameter op = new OracleParameter();

http://6.to/

http://5.to/

op = cmd.Parameters.Add("YRFRM", OracleType.Number);

op.Value = Convert.ToInt32(TextBox15.Text);

op = cmd.Parameters.Add("YRTO", OracleType.Number);

op.Value = Convert.ToInt32(TextBox16.Text);

op = cmd.Parameters.Add("PAN1", OracleType.VarChar);

op.Value = Session["pan"].ToString();

Sal_Ds ds = new Sal_Ds();

adp.Fill(ds, "TOTAL_SALARY_CALCULATIONS");

Code:

1.Employee login

//this code is used for the login process

// Reusable code 1:insert the values


dt = pl.sel(cl).Tables[0];

DataTable dt1 = new DataTable();

co.pempr_pan = TextBox1.Text;

//reusble code 3:to check whether the inserted values present in the table

{

Session["pan"] = TextBox1.Text;

if (dt.Rows.Count == 1)

{

//reusable code 2:to enter to the next page

}

}

else if (dt.Rows.Count == 1)

{

Session["pan"] = TextBox1.Text;

//reusable code 2:to enter to the next page

}

else

{

Label3.Visible = true;

Label3.Text = "incorrect username or password";

}

}

}

2. New Employee registration

protected void Button1_Click(object sender, EventArgs e)

{

if (TextBox17.Text != TextBox18.Text)

{


}

else

{


cemp.pdob = DropDownList2.Text + "/" + DropDownList3.Text + "/" DropDownList4.Text;

if (RadioButton1.Checked == true)

{

cemp.psex = RadioButton1.Text;

}

else

{

cemp.psex = RadioButton2.Text;

}

cemp.pref_no = Convert.ToInt32(TextBox14.Text);

cemp.pcode = DropDownList1.Text;

cl.pemp_pswd = TextBox17.Text;

cl.pemp_id = TextBox16.Text;

pemp.insert(cemp);

pl.insert(cl);


}

}

}

3. tax calculation

//Reusable code 5.to call the procedure and content classes

string p;

DateTime dat;

protected void Page_Load(object sender, EventArgs e)

{

if (IsPostBack == false)

{

Label73.Text = System.DateTime.Now.ToString();

csd.ppan = Session["pan"].ToString() ;

p = csd.ppan;

//reusble code 3:to check whether the inserted values present in the table

{

DataRow dr = dt.Rows[0];

DataTable dddt = new DataTable();

dddt = psd.datesel(p).Tables[0];

DataRow dddr = dddt.Rows[0];

dat = Convert.ToDateTime(dddr[0]);


http://5.to/

csd.ppan = p;

dt1 = psd.sel_all(csd).Tables[0];

if (dt1.Rows.Count > 0)

{

DataRow dr1 = dt1.Rows[0];

//reusable code 4: to take the values into textbox

}

}

}

else

{

}

}

string str,str1;


{

Random r = new Random();

int i = r.Next(999999);

csd.prdm = i;

Session["RDM"] = csd.prdm.ToString();


psd.insert(csd);

Session["dte"] = csd.pdte;

int a,f,g;

float b,c,d,h,j;

a = Convert.ToInt32(TextBox1.Text) + Convert.ToInt32(TextBox2.Text) +

Convert.ToInt32(TextBox3.Text) + Convert.ToInt32(TextBox4.Text) +

Convert.ToInt32(TextBox9.Text);

f=Convert.ToInt32(TextBox5.Text) + Convert.ToInt32(TextBox6.Text) +

Convert.ToInt32(TextBox7.Text)+Convert.ToInt32(TextBox8.Text)+

Convert.ToInt32(TextBox10.Text) +Convert.ToInt32(TextBox11.Text) +



Convert.ToInt32(TextBox16.Text)+



Convert.ToInt32(TextBox21.Text) +






Convert.ToInt32(TextBox32.Text);

g = a - f;

Session["tir"] = g;


string kksal = Session["tir"].ToString();

dt = psd.sel1(csd,kksal).Tables[0];


{

DataRow dr = dt.Rows[0];

str = dr[0].ToString();

}


dt1 = psd.sel2(csd, kksal).Tables[0];


{

DataRow dr = dt1.Rows[0];

str1 = dr[0].ToString();

}

float z, y, x;

z = Convert.ToSingle(10) / Convert.ToSingle(100);

y = Convert.ToSingle(1) / Convert.ToSingle(100);

x = Convert.ToSingle(3) / Convert.ToSingle(100);

j = g - Convert.ToSingle(str1);

Session["tti"] = Convert.ToSingle(str)*y*j;

b=Convert.ToSingle( (g - 1000000) * z);

if (b >= 0)

Session["s_charge"] = b;

else

Session["s_charge"] = 0;

c=g+b;

Session["isp"] = c;

d = Convert.ToSingle(c * x);

Session["edu_cess"] = d;

h= c + d;

Session["ttp"] = h;

Session["btp"] = h;

Session["date"] = Label73.Text;

Session["yrf"] = TextBox33.Text;

Session["yrt"] = TextBox34.Text;

Response.Redirect("Emp_tax.aspx");

}


{


{

MultiView1.SetActiveView(View4);

}

}

decimal TotalPrice,TotalAllow;

public decimal GetPrice(decimal price)

{

TotalPrice += price;

return price;

}

public decimal GetTotal()

{

return TotalPrice;

}

public decimal GetPriceAllow(decimal allw)

{

TotalAllow += allw;

return allw;

}

public decimal GetTotalAllow()

{

return TotalAllow;

}

protected void Button1_Click1(object sender, EventArgs e)

{



for (int i = 1; i <= 12; i++)

{

DropDownList1.SelectedIndex = (i - 1);

ctsc.pfor_month = (DropDownList1.SelectedValue);

ptsc.insert(ctsc);

}


DataGrid2.DataSource = ptsc.sel_total_sal1(ctsc);

DataGrid2.DataBind();

}


{

int i = Convert.ToInt32(TextBox1.Text) + Convert.ToInt32(TextBox2.Text) + Convert.ToInt32(TextBox3.Text) + Convert.ToInt32(TextBox4.Text);

TextBox5.Text = i.ToString();

}


{

int j = Convert.ToInt32(TextBox6.Text) + Convert.ToInt32(TextBox7.Text) + Convert.ToInt32(TextBox8.Text) + Convert.ToInt32(TextBox9.Text) + Convert.ToInt32(TextBox10.Text) + Convert.ToInt32(TextBox11.Text);

TextBox12.Text = j.ToString();

}

}


{


}


{

ctsc.pyr_frm=Convert.ToInt32( TextBox15.Text);

ctsc.pyr_to=Convert.ToInt32( TextBox16.Text);

ctsc.ppan = Session["pan"].ToString();

DataTable dt5=ptsc.sel_total_sal1(ctsc).Tables[0];


{


DataGrid2.DataSource = ptsc.sel_total_sal1(ctsc).Tables[0];


TextBox29.Text = (TotalAllow-TotalPrice).ToString();


TextBox29.Visible = true;

}

else

{


}

}

protected void DataGrid2_ItemCommand(object source, DataGridCommandEventArgs e)

{

if (e.CommandName == "Edit")

{

TextBox tx = (TextBox)(e.Item.Cells[2]).FindControl("TextBox18");

TextBox tx1 = (TextBox)(e.Item.Cells[2]).FindControl("TextBox19");










int tot1 = Convert.ToInt32(tx.Text) + Convert.ToInt32(tx1.Text) + Convert.ToInt32(tx2.Text) + Convert.ToInt32(tx3.Text);

int tot2 = Convert.ToInt32(tx4.Text) + Convert.ToInt32(tx5.Text) + Convert.ToInt32(tx6.Text) + Convert.ToInt32(tx7.Text) + Convert.ToInt32(tx8.Text) + Convert.ToInt32(tx9.Text);

ctsc.ptot1 = tot1;

ctsc.ptot2 = tot2;


ptsc.update(ctsc);




}

}

public void grid()

{

}


{


//reusable code 6:to take the values into crystal report

ReportDocument rpt = new ReportDocument();

rpt.FileName = Server.MapPath("Sal_CR.rpt");

rpt.SetDataSource(ds);

CrystalReportViewer1.ReportSource = rpt;

}

4.Salary Calculation

//Code for total salary calculation


{


{


}

}

decimal TotalPrice,TotalAllow;

public decimal GetPrice(decimal price)

{

TotalPrice += price;

return price;

}

public decimal GetTotal()

{

return TotalPrice;

}

public decimal GetPriceAllow(decimal allw)

{

TotalAllow += allw;

return allw;

}

public decimal GetTotalAllow()

{

return TotalAllow;

}

protected void Button1_Click1(object sender, EventArgs e)

{




for (int i = 1; i <= 12; i++)

{

DropDownList1.SelectedIndex = (i - 1);

ctsc.pfor_month = (DropDownList1.SelectedValue);

ptsc.insert(ctsc);

}


DataGrid2.DataSource = ptsc.sel_total_sal1(ctsc);


}

//To calculate total earnings


{

int i = Convert.ToInt32(TextBox1.Text) + Convert.ToInt32(TextBox2.Text) + Convert.ToInt32(TextBox3.Text) + Convert.ToInt32(TextBox4.Text);

TextBox5.Text = i.ToString();

}

//To calculate total deductions


{

int j = Convert.ToInt32(TextBox6.Text) + Convert.ToInt32(TextBox7.Text) + Convert.ToInt32(TextBox8.Text) + Convert.ToInt32(TextBox9.Text) + Convert.ToInt32(TextBox10.Text) + Convert.ToInt32(TextBox11.Text);

TextBox12.Text = j.ToString();

}

//to show the one year salary details in datagrid


{


}


{

ctsc.pyr_frm=Convert.ToInt32( TextBox15.Text);

ctsc.pyr_to=Convert.ToInt32( TextBox16.Text);


DataTable dt5=ptsc.sel_total_sal1(ctsc).Tables[0];


{




TextBox29.Text = (TotalAllow-TotalPrice).ToString();


TextBox29.Visible = true;

}

else

{


}

}

//To edit the datagrid values

protected void DataGrid2_ItemCommand(object source, DataGridCommandEventArgs e)

{

if (e.CommandName == "Edit")

{

TextBox tx = (TextBox)(e.Item.Cells[2]).FindControl("TextBox18");











int tot1 = Convert.ToInt32(tx.Text) + Convert.ToInt32(tx1.Text) + Convert.ToInt32(tx2.Text) + Convert.ToInt32(tx3.Text);

int tot2 = Convert.ToInt32(tx4.Text) + Convert.ToInt32(tx5.Text) + Convert.ToInt32(tx6.Text) + Convert.ToInt32(tx7.Text) + Convert.ToInt32(tx8.Text) + Convert.ToInt32(tx9.Text);

ctsc.ptot1 = tot1;

ctsc.ptot2 = tot2;


ptsc.update(ctsc);




}

}

public void grid()

{

}

//code for crystel report


{


//Reusable code 6:to take the values into crystal report

ReportDocument rpt = new ReportDocument();

rpt.FileName = Server.MapPath("Sal_CR.rpt");

rpt.SetDataSource(ds);

CrystalReportViewer1.ReportSource = rpt;

}

}

}

CHAPTER 4

TESTING

4.1 Introduction

The chapter testing describes various testing methodologies which are adapted and detailed view of test data’s within each database. During testing of a program to be tested is executed with a set of test data and the output of the program for test data is evaluated.

4.2 Unit Testing

Unit Testing is a procedure used to validate that individual units of source code are working properly. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual program, function, procedure, etc., while in object-oriented programming, the smallest unit is a method; which may belong to a base/super class, abstract class or derived/child class. Ideally, each test case is independent from the others; mock objects and test harnesses can be used to assist testing a module in isolation. Unit testing is typically done by developers and not by Software testers or end-users

4.3 Integration Testing

Integration testing is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing. The purpose of integration testing is to verify functional, performance and reliability requirements placed on major design items

4.4 Validation and testing

Software validation is achieved through a series of tests that demonstrate conformity with requirements. Validation succeeds when software functions in a manner that can be reasonably expected by the end user. Testing is necessary for the success of the system. During testing of a program to be tested is executed with a set of test data and the output of the program for test data is evaluated to determine if the programs are performing as expected.

First the application goes through a phase often referred as alpha testing in which the errors and failures based on simulated user requirements are verified and studied. The modified software is then subjected to phase two called beta testing in the actual user’s site or live environment. After a scheduled time, failures and errors are documented for final correction and enhancements are made before the package is released

In our project, validation and checks have been done inorder to ensure that the developed system is performing up to its expectation. Validations have been done in the area of

login sections and registration sections . In registration forms, certain rules have been set like no field is left blank. In this way each field in the registration form are checked, checking for user name availability and reporting status. In the login pages appropriate messages are displayed when a user provides an invalid response.

4.5 System Testing

System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic.

It is the process of executing the program with the intent of finding errors Testing cannot show the absence of defects; it can only show that software errors are present.

Test Type

Functionality testing. Usability testing. Interface testing Compatibility testing.

Functionality Testing

Tested forms in all pages:

Forms are the integral part. Firstly checked all the validations on each field like user name and password, checking whether all mandatory fields are filled and so on. Checked by providing wrong inputs to the fields in the forms and found they are responding appropriately. Wrong input include like proving an invalid user name or password.

Checks have been made to ensure whether the database functions are working. Like when a new user registers with the site there is database query regarding this. So, these queries are tested by looking into the actual database whether all entries have been affected to the database. If this is not the case, query is checked and rectified. Database checking was positive.

Interface Testing:

The main interfaces are: web based application interface and database interface. In this project, ORACLE server is used. ORACLE server should hold all the C# files which will be interacting with the application logic in the ASP .NET. All these interactions between has been checked and found to be working properly. Errors are also handled properly.

4.6 Test data

4.6.1 User Registration

TABLE 4.1 USER REGISTRATION

F_name M_name L_name Flat_No Building Road District State Pin

Rohan M Ram 342 Skyline Gandhi Calicut Kerala 675343

Anu P S 123 Queen Selam ThamilNadu 345435

Anjali C R 5443 Mattathil Aluva Eranakulam Kerala 45

Mohan K R 565 Apple MC Eranakulam Kerala 675564

Sanu P Aaa Allase RM Banglore Karnadaka 567654

Saam R M 7666 Skyline Ram Ajmer Rajastan 678745

Emp_PAN Sex Emp_category Tel_No DOB Remark

EMP453 Male A person who is.. 04842754342 16/12/1969 Valid

ABC Female A women belo.. 09895674532 07/05/1985 Invalid

12345 Female A women belo.. 04872345432 23/11/1982 Invalid

4554 Male A men below t.. 04567863455 09/09/1979 Valid

Qwer Male A person who is.. 98 12/08/1959 Invalid

9889 Male A men below t.. 91989876545 Invalid

4.6.2 User Login

TABLE 4.2 USER LOGIN

Emp_id Pswd Remark

EMP453 123456 Valids

Aaaa Qwer Invalid

4554 098765 Valid

123 Invalid

EMP453 Aaaaa Invalid

4554 123 Invalid

4.6.3 Slab Updates

TABLE 4.3 SLAB UPDATES

Ass_yr_frm Ass_yr_to Tpe Sal_frm Sal_to Rte Remark

2010 2011 For men below t.. 0 200000 0 Valid

2000 A person who is.. 0 220000 0 Invalid

2010 2011 For men below t.. 200000 350000 23 Valid

2000 2001 For women belo.. 190000 250000 Invalid

2000 2001 A person who is.. 0 0 0 Invalid

2004 2005 For women belo.. Aaa 23000 89 Invalid

4.6.4 Salary Calculation

TABLE 4.4 SALARY CALCULATION

YR_FRM YR_TO FOR_MONTH PAY DA HRA IRI K_G SLI

2000 2001 May 25000 3000 4000 0 0 0

40000 2000 March 30000 5000 15000 800 0 1000

2008 2009 April aaaa 4000 2000 4000 0 2000

1989 May 20000 0 0 3000 1000 0

1999 2000 June 30000 4000 0 0 0

2004 2005 July 45000 0 0 0 0 0

LIC FBS HBA TOT1 TOT2 Remark

1000 2000 0 34000 3000 Valid

2000 0 2000 40000 4000 Invalid

0 0 0 0 0 Invalid

0 5000 5000 0 0 Invalid

3000 1000 0 34000 4000 Valid

0 0 0 0 Invalid

4.6.5 Tax Calculation

TABLE 4.5 TAX CALCULATION

YR_FRM YR_TO PRN AP DED TCP TNA AOI GLI LS

2000 2001 500 200 5000 100 0 0 8000 0

1990 2000 1000 0 0 0 0 0 0 1000

2002 2003 2000 aaa 0 0 1000 0 0 0

1989 1990 100 200 0 1000 0 2000 0 0

1999 199999 40000 0 0 800 0 0 0 0

2010 2011 3000 100000 0 0 0 0 0 0

FA RP EA PTP AOI M_CLAIM EXPND_MEDI EXPND_MEDI2 NSC CONTR

1000 0 0 20000 0 0 0 0 0 0

awe 0 0 0 0 0 0 0 0 0

1000 6000 0 0 1000 0 0 1000 0 0

aaa 100 0 0 0 0 0 0 0 0

7000 8000 0 0 0 5000 0 0 1000 0

0 0 0 1000 0 0 0 0 2000 0

LOAN_INTRST DONATION DEPO PLAN M_FUND P_FUND T_FEE H_LOAN CONTRIBUTION

10000 0 0 0 0 0 50000 0 0

0 0 0 0 0 0 0 0 0

0 0 0 0 0 0 10000 0 0

0 1000 0 0 0 0 0 1000 0

0 0 0 0 0 0 0 0 1000

0 0 0 0 0 0 5500 0 0

S_OR_D MUT_FUND PPF BONDS SEN_CITIZEN P_OFFICE LIP HRA

1000 0 1000 0 0 0 0 2000

0 0 0 0 0 0 Aaa 0

0 0 0 1000 0 0 1000 50000

0 0 0 0 0 0 0 0

0 15000 20000 0 0 0 1800 0

1000 0 0 0 0 0 1000 0

GIS LIC HBA DTE RDM TTI S_CHARGE ISP EDU_CESS

1000 1000 5000 5/23/2011 3:53.. 1560 1000 500 2000 500

0 0 0 4/23/2011 4:34.. 6700 0 0 0 0

1000 100 0 5/13/2011 6:15.. 7566 0 0 0 0

0 0 0 6/12/2011 4:23.. 8976 0 0 0 0

0 5000 0 4/19/2011 5:46.. 9823 1450 0 0 0

8000 1000 5000 3/18/2011 3:26.. 1094 1560 300 1000 4000

TTP BTP BIT TIR DED Remark

1000 300 0 0 0 Valid

0 0 0 0 0 Invalid

12000 900 70000 0 0 Invalid

3000 2500 0 0 0 Invalid

0 0 0 0 0 Invalid

1000 4000 0 0 0 Valid

4.7 Conclusion

Various subsections of the chapter provides an overview of validation and testing process.

CHAPTER 5

IMPLEMENTATION

5.1 Introduction

Implementation is a process of converting a new system into an operational one. The designed system is converted into an operational one using a suitable programming language. Implementation includes all those activities that take place to convert an old system into a new one. Proper implementation is necessary to provide a reliable system to meet organizational requirement

5.2 Implementation plan:

As our project is website oriented, our project is free to use. User only needs a system with minimum requirements and an internet access. User can use any web browser. Since we are not incorporating any complex hardware parts, it can be implemented anywhere very easily. Expertise knowledge is not needed to handle our project. A user with his/her basic knowledge can access it and use it safely.

It is accessible anywhere. One can use it at home, at work or anywhere. The user can use this without any training. Only thing user has to do is to just enter their data where it is required.

Using the given values the tax and salary are calculated automatically. Then who wish to plan his/her tax can do planning and can print the produced report.

User can also refer for the current tax slabs. So it will be very helpful for salaried person in tax calculation and planning.

In the implementation plan the requirements for implementing the project is determined and also tested to confirm the effectiveness while implementing the project design into the source code. The main goal of the implementation plan is the development of source code that is easy to read and understand. The implementation plan will help the project to proceed with the available resources. Once the implementation plan is over the source code can be developed easily because it will provide a clear idea about the project. The implementation of the proposed system is achieved via to the C#.net platform as front end and Oracle 10G as backend. Front end consist of language tools and mechanisms for manipulating the backend.

5.3 Conclusion

Implementation describes about the whole activities necessary to provide a reliable system to meet the necessary requirement.

CHAPTER 6

OPERATIONS MANUAL

6.1 Introduction

The user manual provides user-friendly input and output forms that have been designed with interactive dialogue. It enables the end users to insert details very easily through corresponding interface forms

.

6.2 Screen shots

This is the login page used by the employee

Fig 6.1 log in

This form is used by the administrator to update the tax details

Fig.6.2 Tax slab

This particular form displays the tax updation done by the administrator

Fig 6.3 Updation

This table is used by a new employee for his registration

Fig 6.4 Employee registration

This form is used to enter a particular assessment year to calculate income tax

Fig 6.5 Assessment

This form is used to calculate total salary

Fig 6.6 Total salary calculation

This form shows the tax details of a particular assessment year

Fig 6.7 Tax details

This form is a crystal report displaying the particulars of salary drawn

Fig 6.8 Salary drawn

This particular form is used for tax calculations where the user inputs various details

Fig 6.9 Tax calculation

This form is used to submit as tax statement

Fig 6.10 Tax statement

This form is used by the employee to give some additional information’s

Fig 6.11 Balance to be paid

This is a crystal report showing the tax statement for a particular financial year

Fig 6.12 Tax statement for financial year

Appendix 1

REFERENCE

www.incometaxindia.gov.in s

www.tin-nsdl.com

BIBLIOGRAPHY

1. Professional ASP.NET 2.0

By Bill Evjen, Scoll hanselman,Farhan muhammed, Srinivas, Devin Rader.

Wiley Publishing Inc 2006.

2. Professional C# 2005

By Christ Nagan, Bill Evjen, Jay Glynn,Karley Watson,Morgan Skinner,Allen Jones.

Wiley Publishing Inc 2006.

3. Software Engineering –a practitioner’s Approach

By Roger S.IIpressman.

The Mc.Graw Hill Companies, 6th Edition, 2005.

4. Fudamentals of Database Systems

By Ramez Elmsari,Shamkanth B.Navathe,Durvasulu V.L.N Somayajulu,Shyam K.Guptha.

The McGraw Hill Companies, 3rd Edition, 2007.

http://ASP.NET/

http://www.tin-nsdl.com/

http://www.incometaxindia.gov.in/

TABLE OF CONTENTS

CHAPTER 1: REQUIREMENT ANALYSIS

1. Introduction 12. Feasibility study 23. Project plan 44. User Interview 5 5. Existing system 6 6. Problems in the existing system 7

1.7 New requirements 8

8. Proposed system 89. Requirement analysis 910. Software and Hardware requirements 911. General Description 1012. Specific requirements 1013. Product Function 12 14. Identification of Entities & Attributes 1215. Context Analysis Diagram (CAD) 1516. Data Flow Diagram (DFD) 1617. Entity-Relationship Diagram (ERD) 1918. Conclusion 20

CHAPTER 2: DESIGN SPECIFICATION

2.1 Introduction 21

2.2 Database design 22

2.3 Process design 30

2.4 Conclusion 33

CHAPTER 3: CODING

3.1 Introduction 34

CHAPTER 4: TESTING

4.1 Introduction 48

4.2 Unit testing 48

4.3 Integration testing 48

4.4Validation testing 48

4.5 System testing 49

4.6 Test data 50

4.7 Conclusion 54

CHAPTER 5: IMPLEMENTATION

5.1 Introduction 55

5.2implementation plan 55

5.3 Conclusion 56

CHAPTER 7: OPERATION MANUAL

7.1 Introduction 57

7.2 Screenshots 57

APPENDIX 1: BIBILIOGRAPHY

LIST OF TABLES

1. Table 1.1 Project plan 42. Table 1.2 Entities&Attributes 12

3. Table.2.1 Employee login 24 4. Table.2.2 Employee 255. Table.2.3 Total salary calculations 256. Table.2.4 Deducted salary 267. Table.2.5 Deducted Salary record 278. Table.2.6 Slab updates 299. Table.2.7 T_cal 2910. Table4.1 User registration 5011. Table4.2 user login 5112. Table4.3 Slab Updates 5113. Table4.4 Salary calculation 5214. Table4.5 Tax calculation 53

LIST OF FIGURES

1. Fig 1.1 CAD 16 2. Fig 1.2 DFD 183. Fig 1.3 ERD 204. Fig2.1 slab updation 31 5. Fig2.2 Registration 31 6. Fig2.3 Salary calculation 327. Fig2.4 Tax calculation 328. Fig6.1 Login 579. Fig6.2Tax slab 5810. Fig6.3Updation 5811. Fig6.4Employee registration 5912. Fig6.5Assessment 5913. Fig6.6Total salary calculation 6014. Fig 6.7Tax details 6115. Fig6.8Salary drawn 62

16. Fig6.9Tax calculation 63

17. Fig.6.10Tax statement 6418. Fig6.11Balance to be paid 6519. Fig6.12Tax statement for financial year 65

LIST OF SYMBOLS

1. Process2. Data Flow s3. Data Store 4. Report

LIST OF ABBREVATIONS

1. CAD - Context analysis diagram2. DFD - Data flow diagram3. ERD - Entity relationship diagram4. SDLC - System Development Life Cycle 5. SRS - Software Requirements Specifications

IEE Project Report Format

Documents

Transcript of IEE Project Report Format