CHAPTER 1

INTRODUCTION

1.1 COMPANY PROFILE

Founded in 2000, PSR INFOTECH located at Coimbatore, has a rich background in

Software Development and continues its entire attention on achieving transcending excellence in
the Development and Maintenance of Software Projects and Products in Many Areas.

In Today's Modern Technological Competitive Environment, Students in Computer

Science Stream Want To Ensure That They Are Getting Guidance In An Organization That Can
Meet Their Professional Needs. With Our Well Equipped Team of Solid Information Systems
Professionals, Who Study, Design, Develop, Enhance, Customize, Implement, Maintain and
Support Various Aspects of Information Technology, Students Can Be Sure.

One’s Understand The Students’ Needs, And Develop Their Quality Of Professional Life
By Simply Making The Technology Readily Usable For Them. Practice Exclusively in Software
Development, Network Simulation, Search Engine Optimization, Customization And System
Integration. Our Project Methodology Includes Techniques For Initiating A Project, Developing
The Requirements, Making Clear Assignments To The Project Team, Developing A Dynamic
Schedule, Reporting Status To Executives And Problem Solving.

The indispensable factors, which give the competitive advantages over others in the
market, may be slated as:

 Performance
 Pioneering efforts
 Client satisfaction
 Innovatrice concepts
 Constant Evaluations
 Improvisation

1
ABOUT THE PEOPLE:

As a team have the clear vision and realize it too. As a statistical evaluation, the team has
more than 40,000 hours of expertise in providing real-time solutions in the fields of Android
Mobile Apps Development, Networking, Web Designing, Secure Computing, Mobile
Computing, Cloud Computing, Image Processing And Implementation, Networking With
OMNET++ Simulator, client Server Technologies in Java,(J2EE\J2ME\EJB), ANDROID,
DOTNET (ASP.NET, VB.NET, C#.NET), MATLAB, NS2, SIMULINK, EMBEDDED,
POWER ELECTRONICS, VB & VC++, Oracle and operating system concepts with LINUX.

OUR VISION:

“Impossible as Possible” this is our vision; They work according to our vision.

1.2 OBJECTIVES

This Project is aimed to investigate the development and usage of modern information
technologies in tax management, and modernization of tax administrations. Specifically, the
project tries to investigate e-declaration and e-tax payment systems. E-declaration (or online tax
filing, e-tax return filing, e-filing) can be defined as the tax-return filing system by aid of
computer and internet. Revenue Appraisal system is a payment system (or online tax payment
system) is an information system by which tax-payers would pay electronically tax-due.

There are three tax payment methods. One of them is named traditional tax collection
method, in which the tax-payers pay tax-due at the tax administration. The other two tax payment
methods are to use interactive bank accounts in internet or to use bank ATM in front of the bank
building. These two last methods differ from the traditional method and form online tax payment
system. Government has authorized banks or special financial institutions to collect electronic
taxes

Two methods of data collection were employed in this study. Initially, textual analysis
was applied in order to examine reports, government policy documents, media releases, journal

2
articles, and other written material. Then, in-depth interviews with the directors of tax
administrations and surveys with Certified Public Accountants (CPA) were carried out.

It demonstrates the projects that the government has carried out to use the ICT
technologies in tax management and to modernize the tax management. Then, the project
explains the government's plans and goals relating to e-taxation, and the operation of e-
declaration system. Finally, the paper makes an empirical assessment of adoption of e-tax filing
system with Technology Acceptance (TAM) Model.

It is a web based online project. The main aim of the project is any customer they can access the
system through website at any time without going to the company. As a new customer also he
can collect all information like as a new policy details, agent address and phone no also.

This project deals with Tax payment, here process is first customer will sign in to the system then
he enters his profile, uploads documents, and schedules his interview. Initial status of customer
after registration is “new”. These profile and documents can be viewable by admin. Admin will
assign interviewer to customer and changes customer status to “assign interview”. Then
interviewer will conduct interview to customer and gather all his expenses information and
changes customer status to “interview completed”. Then admin will prepare tax summary and
changes status to “finished”.

The major part of the system is the system can accessible in outside by the customer only but
whereas within the premises it is possible by the Administrator, Interviewer only.

3
 CHAPTER 2

SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

Present system is manual. The Project Metrics has to enter all the details of project,
documents, and tasks. It maintains the team information and also efforts estimation. For this
purpose the organization maintain the size of the document, source code and update the
information about team member’s details manually. Which is much of time consuming process
and more importantly it is error prone.

Drawbacks

 It is time consuming
 It leads to error prone results
 It consumes lot of manpower to better results
 It lacks of data security
 Retrieval of data takes lot of time
 Percentage of accuracy is less
 Reports take time to produce

2.2 PROPOSED SYSTEM

After understanding the existing system and understanding the need for developing a new
system different people involved in the related activities have been consulted. The data needed
for the study has been collected from company records.

The computerization of this system would avoid the wrong interpretation and bad calculation
of data .The system help the user to see any documents, source code, tasks, activities, team
information with details at the click of a button. The record data is maintained and backed up
such a way that data is not loss. The speed of the system could also increase.

4
Advantages

 To generate the quick reports

 To make accuracy and efficient calculations
 To provide proper information briefly
 To provide data security
 To provide huge maintenance of records
 Flexibility of transactions can be completed in time

2.3 FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put forth
with a very general plan for the project and some cost estimates. During system analysis the
feasibility study of the proposed system is to be carried out. This is to ensure that the proposed
system is not a burden to the company. For feasibility analysis, some understanding of the major
requirements for the system is essential.
Three key considerations involved in the feasibility analysis are

 Economical feasibility

 Technical feasibility

 Social feasibility

2.3.1 Economical Feasibility

This study is carried out to check the economic impact that the system will have on the
organization. The amount of fund that the company can pour into the research and development
of the system is limited. The expenditures must be justified. Thus the developed system as well
within the budget and this was achieved because most of the technologies used are freely
available. Only the customized products had to be purchased.

5
2.3.2 Technical Feasibility

This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the available
technical resources. This will lead to high demands on the available technical resources. This will
lead to high demands being placed on the client. The developed system must have a modest
requirement, as only minimal or null changes are required for implementing this system.

2.3.3 Social Feasibility

The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system and
to make him familiar with it. His level of confidence must be raised so that he is also able to
make some constructive criticism, which is welcomed, as he is the final user of the system.

6
 CHAPTER 3

SYSTEM SPECIFICATION

3.1 HARDWARE REQUIREMENTS

System : Pentium® Dual-Core CPU 2.30 GHz.

Hard Disk : 300 GB.

Mouse : Optical Mouse.

RAM : 2.00 GB.

Keyboard : Standard 102 keys.

3.2 SOFTWARE REQUIREMENTS

Operating system : Windows XP.

Front-End : Asp.net.

Back-End : SQL.

Data Base : SQL Server 2000.

7
 CHAPTER 4

SOFTWARE DESCRIPTION

4.1 FRONT END

The .Net Framework

The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet.

Objectives of .Net Framework

 To provide a consistent object-oriented programming environment whether object

codes is stored and executed locally on Internet-distributed, or executed remotely.

 To provide a code-execution environment to minimizes software deployment and

guarantees safe execution of code.

 Eliminates the performance problems.

There are different types of application, such as Windows-based applications and Web-
based applications. To make communication on distributed environment to ensure that code be
accessed by the .NET Framework can integrate with any other code.

Components of .Net Framework

The Common Language Runtime (CLR)

The common language runtime is the foundation of the .NET Framework. It

manages code at execution time, providing important services such as memory
management, thread management, removing and also ensures more security and
robustness.

8
 The concept of code management is a fundamental principle of the runtime. Code
that targets the runtime is known as managed code, while code that does not target the
runtime is known as unmanaged code.

The .Net Frame Work Class Library

It is a comprehensive, object-oriented collection of reusable types used to develop

applications ranging from traditional command-line or graphical user interface (GUI)
applications to applications based on the latest innovations provided by ASP.NET, such
as Web Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load the
common language runtime into their processes and initiate the execution of managed
code, thereby creating a software environment that can exploit both managed and
unmanaged features. The .NET Framework not only provides several runtime hosts, but
also supports the development of third-party runtime hosts. Internet Explorer is an
example of an unmanaged application that hosts the runtime (in the form of a MIME type
extension)

Features of The Common Language Runtime

The common language runtime manages memory; thread execution, code execution, code
safety verification, compilation, and other system services these are all run on CLR.

 Security.
 Robustness.
 Productivity.
 Performance.
Security

The runtime enforces code access security. The security features of the runtime thus
enable legitimate Internet-deployed software to be exceptionally feature rich. With
regards to security, managed components are awarded varying degrees of trust, depending

9
 on a number of facto that include their origin to perform file-access operations, registry-
access operations, or other sensitive functions.

Robustness

The runtime also enforces code robustness by implementing a strict type- and
code-verification infrastructure called the common type system(CTS). The CTS ensures
that all managed code is self-describing. The managed environment of the runtime
eliminates many common software issues.

Productivity

The runtime also accelerates developer productivity. For example, programmers can
write applications in their development language of choice, yet take full advantage of the
runtime, the class library, and components written in other languages by other developers.

Performance

The runtime is designed to enhance performance. Although the common language

runtime provides many standard runtime services, managed code is never interpreted. A
feature called just-in-time (JIT) compiling enables all managed code to run in the native
machine language of the system on which it is executing. Finally, the runtime can be
hosted by high-performance, server-side applications, such as Microsoft® SQL Server™
and Internet Information Services (IIS).

Visual Studio .Net

Visual Studio .NET is a complete set of development tools for building ASP Web
applications, XML Web services, desktop applications, and mobile applications In addition to
building high-performing desktop applications, you can use Visual Studio's powerful component-
based development tools and other technologies to simplify team-based design, development, and
deployment of Enterprise solutions.

Visual Basic .NET, Visual C++ .NET, and Visual VB .NET all use the same integrated
development environment (IDE), which allows them to share tools and facilitates in the creation

10
of mixed-language solutions. In addition, these languages leverage the functionality of the .NET
Framework and simplify the development of ASP Web applications and XML Web services.

Visual Studio supports the .NET Framework, which provides a common language
runtime and unified programming classes; ASP.NET uses these components to create ASP Web
applications and XML Web services. Also it includes MSDN Library, which contains all the
documentation for these development tools.

ASP.Net

ASP.NET is the next version of Active Server Pages (ASP);it is a unified web
development platform that provides the services necessary for developers to build enterprise class
Web applications. While ASP.NET is largely syntax compatible, it also provides a new
programming model and infrastructure for more secure, scalable and stable
applications.ASP.NET is compiled, .NET based environment, one’s can author applications in
any .NET compatible language, including Visual Basic .NET, c#, and Jscript .NET.

Data Access With Ado.Net

As you develop applications using ADO.NET, you will have different requirements for
working with data. You might never need to directly edit an XML file containing data - but it is
very useful to understand the data architecture in ADO.NET.ADO.NET offers several advantages
over previous versions of ADO:

Interoperability

ADO.NET applications can take advantage of the flexibility and broad acceptance of
XML. Because XML is the format for transmitting datasets across the network, any component
that can read the XML format can process data. The receiving component need not be an
ADO.NET component.

Performance

ADO.NET datasets offer performance advantages over ADO disconnected record sets. In
ADO.NET data-type conversion is not necessary.

11
Scalability

ADO.NET accommodates scalability by encouraging programmers to conserve limited

resources. Any ADO.NET application employs disconnected access to data; it does not retain
database locks or active database connections for long durations.

Visual Basic.Net

Visual VB includes many new features. The Visual VB supports interfaces but not
implementation inheritance. Visual VB supports implementation inheritance, interfaces and
overloading. In addition, Visual VB .NET supports multithreading concept.

Common Language Specification (CLS)

Visual VB.NET is also compliant with CLS (Common Language Specification) and
supports structured exception handling. CLS is set of rules and constructs that are supported by
the CLR (Common Language Runtime). CLR is the runtime environment provided by the .NET
Framework; it manages the execution of the code and also makes the development process easier
by providing services.

Visual VB.NET is a CLS-compliant language. Any objects, classes, or components that

created in Visual VB.NET can be used in any other CLS-compliant language. In addition, one
can use objects, classes, and components created in other CLS-compliant languages in Visual
VB.NET .The use of CLS ensures complete interoperability among applications, regardless of the
languages used to create the application.

Implementation Inheritance

Visual VB.NET supports implementation inheritance. This means that, while creating
applications in Visual VB. NET, one

can drive from another class, which is know as the base class that derived class inherits
all the methods and properties of the base class. In the derived class, they can either use the
existing code of the base class or override the existing code. Therefore, with help of the
implementation inheritance, code can be reused.

12
4.2 BACK END

Features of Sql - Server

Microsoft SQL Server is a relational model database server produced by Microsoft. Its
primary query languages are T-SQL and ANSI SQL.The OLAP Services feature available in
SQL Server version 7.0 is now called SQL Server 2000 Analysis Services. The term OLAP
Services has been replaced with the term Analysis Services. Analysis Services also includes a
new data mining component. The Repository component available in SQL Server version 7.0 is
now called Microsoft SQL Server 2000 Meta Data Services. References to the component now
use the term Meta Data Services.

Internet Integration

The SQL Server 2000 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 SQL Server 2000 programming model is integrated with the Windows
DNA architecture for developing Web applications, and SQL Server 2000 supports features such
as English Query and the Microsoft Search Service to incorporate user-friendly queries and
powerful search capabilities in Web applications.

Scalability and Availability

The same database engine can be used across platforms ranging from laptop computers
running Microsoft Windows® 98 through large, multiprocessor servers running Microsoft
Windows 2000 Data Center Edition. SQL Server 2000 Enterprise Edition supports features such
as federated servers, indexed views, and large memory support that allow it to scale to the
performance levels required by the largest Web sites.

Enterprise-Level Database Features

The SQL Server 2000 relational 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.
SQL Server 2000 distributed queries allow you to reference data from multiple sources as if it

13
were a part of a SQL Server 2000 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

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

Data warehousing

SQL Server 2000 includes tools for extracting and analyzing summary data for online
analytical processing. SQL Server also includes tools for visually designing databases and
analyzing data using English-based questions.

14
 CHAPTER 5

PROJECT DESCRIPTION

5.1 PROBLEM DEFINITION

Tax Information System is a professional financial services company established by
experienced CPA’s and chartered accounts to provide cost effective and efficient financial and
tax planning solutions to a wide range of clients across the globe. Tax information system is
providing single window tax service to the Indian software consultants having income from both
India and USA by minimizing the overall tax burden claiming foreign tax credits and other tax
planning strategies according to the US internal revenue code and India income tax Act,1961.
Present system is manual. The Project Metrics has to enter all the details of project, documents,
and tasks. It also maintenance the team information and also efforts estimation. It is time
consuming, It leads to error prone results , It consumes lot of manpower to better results , It
lacks of data security , Retrieval of data takes lot of time , Percentage of accuracy is less.

5.2 OVERVIEW OF PROJECT

This Data Transform System Project is QoS oriented distributed routing protocol (QOD)
for hybrid networks to provide QoS services in a highly dynamic scenario. In the highly dynamic
environment, the link between the nodes changes frequently. So, the route failure will occur in
the network which leads to packet loss during transmission.

To avoid this, a link aware opportunistic relay node selection algorithm is introduced. In
this algorithm, all the nodes not going to maintain the routing table. At the time of transmission,
the source node builds the route to reach the destination by using the parameter link residual life
time.

The Link residual life is defined as “How long the link between the wireless nodes exists
and capability of that link to provide efficient communication without fails. The link residual life
is used to avoid poor link connectivity and reduce the possibility of retransmissions.

15
 CHAPTER 6

SYSTEM DESIGN

The system of objectives outline during the feasibility study serves as the basic from
which the work of system design is initiated. Much of the activities is involved at the stage is
technical nature requiring a certain degree of systems sound knowledge of computer related
technology and through understanding of computer available in the market and the various
facilities provided by the vendors. Nevertheless, a system cannot be designed in isolation without
the active involvement of the user. The user has a vital role to play at the stage too. As it is
known that data collected that during feasibility study wills were utilized systemically during the
system design. It should however be kept in mind that details study of the existing system is not
necessarily over with the completion of the feasibility study. Depending on the plan of feasibility
study, the level of details study will vary and the system design stage will also vary in the amount
of investigation that still needs to be done. This investigation is generally an urgent activity
during the system.

6.1 MODULE DESCRIPTION

 Administrator module
 Interviewer module
 Customer’s information module

Administrator module:

The Administrator is the super user of the system. He is the responsible person to view the
registered customers, view customer’s documents, upload documents, and update the status of the
customers. He can manage the Interviewer registration and assigns interviewer to customers.

16
Interviewer module:

This module is responsible to conduct Interviews to customer in interview he will gather

information from the customer and updates status of the customer. After completion of customer face to
face interview he will send updated information of customer to the Admin.

Customer’s information module:

Customer is the back bone of the company. He can access the system through online to send his
profile, documents and he can do all tax transactions through the system is also possible.

The main goal of the system to maintain all details of customer information from starting to
ending of his tax payment and PDF review is done.

17
 6.2 SYSTEM FLOW DIAGRAM

Revenue appraisal system

User Interviewer

Upload Assign Submitted

Register
documents interview outman

Schedule Payment Tax summery Checking

expenses

6.2.1 System Flow Diagram – Revenue appraisal system

18
6.3 DATAFLOW DIAGRAM
Level 0

Interviewer login

Revenue
User login Appraisal system User login

6.3.1 Dataflow Diagram - Revenue appraisal system

Level 1

View customer
detais
Admin login
View interviewer DB
details

login
User Login Register the customer DB

Interviewer login Update the customer

DB
details

6.3.2 Dataflow Diagram – Revenue appraisal system

19
6.4 DATABASE DESIGN
The most important consideration in designing the database is how information will be
used. The main objectives of designing a database are:

Data Integration:

In a database, information from several files are coordinated, accessed and operated upon
as through it is in a single file. Logically, the information are centralized, physically, the data
may be located on different devices, connected through data communication facilities.

Data Integrity

Data integrity means storing all data in one place only and how each application to access
it. This approach results in more consistent information, one update being sufficient to achieve a
new record status for all applications, which use it. This leads to less data redundancy; data items
need not be duplicated; a reduction in the direct access storage requirement.

Data Independence:

Data independence is the insulation of application programs from changing aspects of

physical data organization. This objective seeks to allow changes in the content and organization
of physical data without reprogramming of applications and to allow modifications to application
programs without reorganizing the physical data.

The tables needed for each module were designed and the specification of each and every
column was given based on the records and details collected during record specification of the
system study.

20
6.5 TABLE STRUCTURE

Name Data Type Allow Nulls

CustomerId Int Not Null

FirstName varchar(50) Null

MiddleName varchar(50) Null

LastName varchar(50) Null

ContactNumber varchar(50) Null

UserId varchar(50) Null

Password varchar(50) Null

UserType varchar(50) Null

CreatedOn Datetime Null

Status varchar(50) Null

6.5.1 Registration Form

Name Data Type Allow Nulls

BankName varchar(50) Not Null

AccountNo varchar(50) Null

RoutingNo varchar(50) Null

AccountType varchar(50) Null

CustomerId Int Null

6.5.2 Bank Information

21
Name Data Type Allow Nulls

Id Int Not Null

CustomerId Int Null

Sex varchar(50) Null

DOB varchar(50) Null

SSN varchar(50) Null

Address varchar(50) Null

City varchar(50) Null

State varchar(50) Null

Zip varchar(50) Null

HomePhone varchar(50) Null

WorkPhone varchar(50) Null

Email varchar(50) Null

AlternateEmail varchar(50) Null

Occupation varchar(50) Null

Marital varchar(50) Null

Dependents varchar(50) Null

6.5.3 Tax Payer Information

22
Name Data Type Null

JobRelatedId Int Not Null

LaptopCost varchar(50) Null

LaptopDateOfPurchase varchar(50) Null

ComputerCost varchar(50) Null

ComputerDateOfPurchase varchar(50) Null

HomeCost varchar(50) Null

HomeDateOfPurchase varchar(50) Null

BusinessCost varchar(50) Null

BusinessDateOfPurchase varchar(50) Null

Cellcost varchar(50) Null

CellDateOfPurchase varchar(50) Null

BooksandSubscriptions varchar(50) Null

InternetCharges varchar(50) Null

CellPhoneCharges varchar(50) Null

HIBExpenses varchar(50) Null

JobTrainingandCertificationExpenses varchar(50) Null

InterviewerNotes varchar(50) Null

InterviewerId Int Null

CustomerId Int Null

CreatedOn varchar(50) Null

6.5.4 Job Related Expense

23
6.8 INPUT DESIGN
Input design is the process of converting the user-oriented input to a computer based
format. The goal of the input design is to make the data entry easier, logical and error free. Errors
in the input data are controlled by the input design. The quality of the input determines the
quality of the system output.

The entire data entry screen is interactive in nature, so that the user can directly enter data
into the page according to the prompted messages. The users are also provided with option of
selecting an appropriate input from a list of values. This will reduce the number of error, which
are likely to arise if they were to be entered by user itself.

The aim of the input design is to ensure the maximum possible levels of accuracy and also
ensures that the input is accessible to be understood by the user.

6.9 OUTPUT DESIGN

Output design is very important in the computerized system, without reliable output, the
user may feel that the entire system is unnecessary and have to avoid using it. The proper output
design is important in any system and it facilitates effective decision making. The output design
of this system includes various reports.

Computer output is the most important and direct source of information to the user.
Efficient and intelligible output design should improve the systems relationships with the user
and helps in decision making.

A major form of output is the hardcopy from the printer.

An application is successful only when it can provide efficient and effective reports.
Reports are actually presentable form of the data. The report generation should be useful to the
management for future reference. The report are the main source of information for user’s
operators and management.

24
 CHAPTER 7

SYSTEM TESTIING

The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product.

It provides a way to check the functionality of components, sub-assemblies, assemblies

and/or a finished product It is the process of exercising software with the intent of ensuring that
the Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific testing
requirement.

7.1 UNIT TESTING

Unit testing, also known as component testing refers to tests that verify the functionality
of a specific section of code, usually at the function level. In an object-oriented environment, this
is usually at the class level, and the minimal unit tests include the constructors and destructors

These types of tests are usually written by developers as they work on code (white-box
style), to ensure that the specific function is working as expected. One function might have
multiple tests, to catch corner cases or other branches in the code. Unit testing alone cannot verify
the functionality of a piece of software, but rather is used to assure that the building blocks the
software uses work independently of each other.

7.2 INTEGRATION TESTING

Integration testing is any type of software testing that seeks to verify the interfaces
between components against a software design. Software components may be integrated in an
iterative way or all together.

Normally the former is considered a better practice since it allows interface issues to be
localized more quickly and fixed. Integration testing works to expose defects in the interfaces and
interaction between integrated components (modules). Progressively larger groups of tested

25
software components corresponding to elements of the architectural design are integrated and
tested until the software works as a system.

7.3 VALIDATION TESTING

To uncover functional errors, that is, to check whether functional characteristics confirm
to specification or not, almost all the inputs are validated strictly and inform the user if there is
any wrong input. The modules are validated such that only after table selection the chart form can
be opened.

7.4 USER ACCEPTANCE TESTING

User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional requirements.
This is to verify that all the system elements have been properly integrated and perform allocated
functions. Testing executes a program to test the logic changes made in it and with intention of
finding errors. Tests are also conducted to find discrepancies between system and its original
objective, current specification and documents.

26
 CHAPTER 8

SYSTEM IMPLEMENTATION

When the initial design was done for the system, the client was consulted for the
acceptance of the design so that further proceedings of the system development can be carried on.
After the development of the system a demonstration was given to them about the working of the
system. The aim of the system illustration was to identify any malfunction of the system.

After the management of the system was approved the system implemented in the concern,
initially the system was run parallel with existing manual system. The system has been tested
with live data and has proved to be error free and user friendly. Implementation is the process of
converting a new or revised system design into an operational one when the initial design was
done by the system; a demonstration was given to the end user about the working system. This
process is uses to verify and identify any logical mess working of the system by feeding various
combinations of test data.

After the approval of the system by both end user and management the system was
implemented. A product software implementation method is a blueprint to get users and/or
organizations running with a specific software product. The method is a set of rules and views to
cope with the most common issues that occur when implementing a software product: business
alignment from the organizational view and acceptance from the human view.

The implementation of product software, as the final link in the deployment chain of
software production, is in a financial perspective of a major issue. The Implementation
methodology includes four phases - Discovery, System Development, User Acceptance Testing
and Production Rollout. It’s easy to be overwhelmed by slick marketing presentations,
particularly when the sales force is talking about things that most people don’t completely
understand. Showmanship gets in the way of real capabilities. Unless the review team is judging
each vendor against the same list of needs, with the same understanding of the significance of
each rating, “likeability” can win over capability.

27
 These implementation phases are designed to provide clients with a seamless transition
from an existing electronic or paper-based system to Sigmund while ensuring all aspects of a
client’s

Operations are accounted for by the software. The Sigmund project team, comprised of
individuals with clinical, billing and operations experience, is equipped with the skills and tools
to manage the entire process from system requirements gathering to deployment. Sigmund
provides various levels of support, depending on client needs, including client-side Project
Management.

The Discovery Phase is preceded by a Project Kick-off Work-session that includes

application demonstrations, completion and review of requirements and configuration
questionnaires, identification of key client documentation, as well as consultation on possible
process re-engineering needs. The Project Kick-off provides your organization with the
opportunity to not only introduce the Sigmund Project Team to your organization, but also to
define and structure your organization’s Project Team. System implementation is made up of
many activities. The six major activities are as follows.

CODING

Coding is the process of whereby the physical design specifications created by the
analysis team turned into working computer code by the programming team.

TESTING

Once the coding process is begin and proceed in parallel, as each program module can be
tested.

INSTALLATION

Installation is the process during which the current system is replaced by the new system.
This includes conversion of existing data, software, and documentation and work procedures to
those consistent with the new system.

28
DOCUMENTATION

It is result from the installation process, user guides provides the information of how the
use the system and its flow.

TRAINING AND SUPPORT

Training plan is a strategy for training user so they quickly learn to the new system.The
development of the training plan probably began earlier in the project.The best-suited application
package to develop the system is VB .NET under Windows XP’ environment.

As part of the proven implementation methodology, every customer gets Administrator

Training for each of the applications they're implementing.The trainer will deliver the
Administrator Training on-site, face-to-face, to a maximum of system administrators,so each
learner gets personalized attention and can ask and get specific answers to questions. If it's more
convenient for them and they can be offered the training facilities.

29
 CHAPTER 9

CONCLUSION AND FUTURE ENHANCEMENTS

9.1 CONCLUSION

This project was about both the individual and organizational performance. It investigates
the e-declarations like e-filling, e-tax returns, e-tax payments with the Technology acceptance
model(TAM). The clients whoa re accessible regarding the company, can gather all information's
through online such as new policy details, agent address and phone number. It is more efficient to
handle the reports and to handle the data which is much more consistent and flexible rather than
proposed system. By single click , every clients of the company ,can view the details of source
code, tasks what are all assigning and their team information's up-to-date. All the transactional
data is secured through the process of online.

9.2 FUTURE ENHANCEMENTS

The proposed project was made through the online process called TAM model. But the
future scope is to integrate the online resources into mobile updation to every user in the
company. If a person is an interviewer, can make the interview to someone who is arrival person
to that company, after that interviewer will update the information's to their higher officials. On
that time we will going to implement the updation through the message to that higher official,
where on that it will be ease to check whether the particular person is relevant to handle their
office resources or not. Also, it leads to produce their results on that time itself. If any persons
need not to wait for long until their results came. The higher official may selected/rejected their
candidate is updated on their profile where it was made, by viewing the message and clicking
application regarding to choose whether he/she is selected or not. Message notification is helpful
when the person is not in online.

30
 CHAPTER 10

APPENDIX

10.1 SOURCE CODE

Login Behind Code:

using System;

using System.Data;

using System.Configuration;

using System.Collections;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Web.UI.HtmlControls;

using System.Data.SqlClient;

public partial class Home_Login : System.Web.UI.Page

static string constr = ConfigurationManager.ConnectionStrings["TestConnection"].ToString();

static SqlConnection con = new SqlConnection(constr);

31
 DataSet ds = new DataSet();

protected void Page_Load(object sender, EventArgs e)

con.Close();

protected void Button1_Click(object sender, EventArgs e)

con.Open();

string str = "select * from TblRegistrationForm where UserId='"+TxtUserName.Text+"' and

Password='"+TxtPassword.Text+"'";

SqlCommand cmd = new SqlCommand(str, con);

SqlDataAdapter adp = new SqlDataAdapter(cmd);

adp.Fill(ds, "TblRegistrationForm");

if (ds.Tables["TblRegistrationForm"].Rows.Count != 0)

Session["CustomerId"] =
ds.Tables["TblRegistrationForm"].Rows[0]["CustomerId"].ToString();

if (ds.Tables["TblRegistrationForm"].Rows[0]["UserType"].ToString() == "C")

Response.Redirect("~/Client/Home.aspx");

32
 }

else if (ds.Tables["TblRegistrationForm"].Rows[0]["UserType"].ToString() == "I")

Response.Redirect("~/Interviewer/Home.aspx");

else if(ds.Tables["TblRegistrationForm"].Rows[0]["UserType"].ToString() == "A")

Response.Redirect("~/Admin/Home.aspx");

else

Page.RegisterClientScriptBlock("a", "<script>alert('Username & Password

Mismatch');</script>");

con.Close();

33
Taxer payer information:

<%@ Page Language="C#" MasterPageFile="~/Client/CustomerMaster.master"

AutoEventWireup="true"

CodeFile="MyProfile.aspx.cs" Inherits="Client_MyProfile" Title="My Profile Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" runat="Server">

<asp:Panel ID="Panel1" runat="server" Height="50px" Style="z-index: 100; left: 204px;

position: absolute; top: -59px" Width="125px">

<asp:Label ID="Label1" runat="server" Font-Bold="True" Font-Names="Arial" Font-

Size="12pt"

ForeColor="Maroon" Text="Welcome to My Profile Page" Width="253px" style="z-

index: 100; left: 0px; position: absolute; top: -15px"></asp:Label>

</asp:Panel>

<asp:Panel ID="Panel2" runat="server" Height="326px" Style="z-index: 100; left: 0px;

position: absolute; top: -17px" Width="447px">

<table style="width: 694px">

<tr>

<td align="center" colspan="6" valign="top">

<asp:Label ID="Label27234" runat="server" CssClass="label" Font-

Bold="True" Font-Names="Arial"

34
 <td style="width: 100px">

<asp:DropDownList ID="ddlYear" runat="server"

CssClass="textbox" Width="44px">

<td align="left" style="width: 100px" valign="top">

<asp:Label ID="Label3158" runat="server" CssClass="label" Font-

Bold="True" Font-Names="Arial"

Text="SSN"></asp:Label>

</td>

<td align="left" colspan="5" valign="top">

<asp:TextBox ID="TxtSsn" runat="server"

CssClass="textbox"></asp:TextBox>

</td>

</tr>

<tr>

<td align="left" style="width: 100px" valign="top">

<asp:Label ID="Label32980" runat="server" CssClass="label" Font-

Bold="True" Font-Names="Arial"

Text="Address"></asp:Label>

</td>

<td align="left" colspan="5" valign="top">

<asp:TextBox ID="TxtAddress" runat="server" CssClass="textbox"

TextMode="MultiLine"

35
 Width="101px"></asp:TextBox>

</td>

</tr>

<tr>

<td align="left" style="width: 100px; height: 22px;" valign="top">

<asp:Label ID="Label95980" runat="server" CssClass="label" Font-

Bold="True" Font-Names="Arial"

Text="City"></asp:Label>

</td>

<td align="left" style="width: 100px; height: 22px;" valign="top">

<asp:TextBox ID="TxtCity" runat="server"

CssClass="textbox"></asp:TextBox>

</td>

<td align="right" style="width: 71px; height: 22px;" valign="top">

<asp:Label ID="Label104" runat="server" CssClass="label" Font-

Bold="True" Font-Names="Arial"

Text="State" Width="139px"></asp:Label>

</td>

<td align="left" style="width: 100px; height: 22px;" valign="top">

<asp:TextBox ID="TxtState" runat="server"

CssClass="textbox"></asp:TextBox>

</td>

36
 <td align="right" style="width: 100px; height: 22px;" valign="top">

<asp:Label ID="Label1154" runat="server" CssClass="label" Font-

Bold="True" Font-Names="Arial"

Text="ZIP"></asp:Label>

</td>

<td align="left" style="width: 100px; height: 22px;" valign="top">

<asp:TextBox ID="TxtZip" runat="server"

CssClass="textbox"></asp:TextBox>

</td>

</tr>

<tr>

<td align="left" style="width: 100px" valign="top">

<asp:Label ID="Label125" runat="server" CssClass="label" Font-

Bold="True" Font-Names="Arial"

Text="Home Phone"></asp:Label>

</td>

<td align="left" colspan="5" valign="top">

<asp:TextBox ID="TxtHomePhone" runat="server"

CssClass="textbox"></asp:TextBox>

</td>

</tr>

<tr>

37
 <td align="left" style="width: 100px" valign="top">

<asp:Label ID="Label1398" runat="server" CssClass="label" Font-

Bold="True" Font-Names="Arial"

Text="Work Phone"></asp:Label>

</td>

<td align="left" style="width: 100px" valign="top">

<asp:TextBox ID="TxtWorkPhone" runat="server"

CssClass="textbox"></asp:TextBox>

</td>

<td align="left" style="width: 71px" valign="top">

</td>

<td align="left" style="width: 100px" valign="top">

</td>

<td align="left" style="width: 100px" valign="top">

</td>

<td align="left" style="width: 100px" valign="top">

</td>

</tr>

<tr>

<td align="left" style="width: 100px" valign="top">

<asp:Label ID="Label145" runat="server" CssClass="label" Font-

Bold="True" Font-Names="Arial"

38
10.2 SCREEN SHOTS

Home

39
Regisgtration Page

40
Login

41
Client Home Page:

TaxPayer Information System:

42
Dependent Information

Vehicle Information:

43
Bank Information

44
Interview page

Schedule Page

45
Payment page

PDF Review

46
Filing Page

47
 CHAPTER 11

REFERENCES

11.1 BOOK REFERENCES

1. software engineering By Roger s. Pressman

2. complete html Steven Holzner

3. unified modeling language By Grady Booch, Ranbaugh, Jacobson

4. sql for professionals By Jain

5. c#.net black book By Evangeleous Petersons

6. msdn 2005 By Microsoft

11.2 WEB REFERENCES

1. http://www.msdn.com
2. http://www.codeproject.com
3. http://w3school.com/SQLServer

48