TAX MANAGEMENT SYSTEM

Submitted By:

TABLE OF CONTENTS
Content no. 1 Content Introduction 1.1Aim of the project 1.2Objective of the project Page no. 4-5

2 3 4

Problem Selection 6-7 Project Monitoring System 8-12 System Study 13-20 2.1 Feasibility test 2.2 Preliminary survey 2.3 Requirement Specification 2.4 System Hardware and Software Required

System Analysis 21-26 3.1 Overall Strategy 3.2 Data Flow Analysis for the Current System System Design 27-40 4.1 Design Analysis 4.2 Entity Relationship Diagram 4.3 Data Flow Diagram 4.4 Data Dictionary System Testing And Implementation 41-48 5.1 Testing 5.2 Unit Testing 5.3 System Testing 5.4 Integration Documentation 49

INTRODUCTION
Aim of the project The aim of the project is to deliver a working system that will allow the organizations (org.) to tabulate tax of its employees with ease. The project targets to lessen the burden on the people of an org. from the lengthy numerical calculation they have to perform while tax calculation. The output obtained through the work of this project will be error-free and hence will be reliable for the organization to help it and its employees regarding taxation. This may include filing tax-returns or keeping database for companys future use. Objective of the project To produce a simple, yet suitably effective user friendly interface, and a system that is easily maintainable, efficient and practical. It takes the value from the data entry operators, calculates the tax and stores it. It simplifies the tedious task of manual work and saves time and increases accuracy and reliability of the data. The proposed system has the following objectives to be achieved. User Friendly Environment Less Space Fast Retrieval Easy to Operate Accuracy Cost Reduction Report generation

PROBLEM

SELECTION

After gathering the details of the existing system a lot of problems come to light. The various problems that came into light are as follows: Difficulty in finding any information at any instance. Lack of appropriate report to submit the management on demand due to large manual processing done on various relevant registers. Difficulty in responding to the query submitted by the outsiders. Difficulty in updating of records. Financial loss due to late manual report generation.

The earlier system of tax calculation were found to be manual, creating lot of error and taking ample amount of time for processing of small app. The data was not reliable. The current system is not organized. It is a system based on more of common sense. Even a small error in the calculation can lead to bigger problems for the concerned organization. Hence leading to loss of an org. Analysis of Fact: After analyzing the present system and interviewing the people it has been found that manual processing is time consuming. The manual method of maintaining record is very tedious and error prone and there was lack in consistency. Accessing a particular record takes enormous amount of time. Since different registers maintain data.

PROJECT

MONITORING

SYSTEM

There are various orders in which the seven phases of the Software Development Life Cycle (SDLC) are implemented. These are what we know as software process models. They evolve around a life cycle that begins with the recognisation of users need and understanding their problems. These models were the basic building blocks of developing and monitoring of the project. The various cycles of SDLC are given below:

FEASIBILITY STUDY

SYSTEM ANALYSIS

SYSTEM DESIGN

DEVELOPMENT

TESTING

IMPLEMENTATION

MAINTENANCE

A software process model is a development strategy we incorporate to describe how a set of activities (the seven phases of SDLC) must be performed and in which order to get the desired output. We already have a few process models defined and described. They are: 1.1. 1.2. 1.3. 1.4. 1.5. Code and Fix Model Waterfall Model Evolutionary Model Transformation Model Spiral Model

To select the best model for the project all the above mentioned models is to be evaluated. After evaluation the following assessment is realized. The Code and Fix Model can actually be considered no model at all as there is nothing rigid and the developer has to follow his inspirations. The Evolutionary model is increment driven and a kind of trial and error method. The Transformation model can be called specification driven, as the development specifications. Spiral model is a Meta model that may be called risk driven. Since, there is time constraint, trial and error and risk driven models are eliminated. The project must have documentation and this feature is facilitated only by the Waterfall model. This model is named waterfall model because its diagrammatic representation resembles a cascade of waterfall. The phases always occur in process occurs through iterative refinement of formal

an order and do not overlap. The developer must complete each phase before the next phase begins. The model is briefly described which will facilitate the reader to follow the exact path I am going to follow in the development of the system.

THE WATERFALL MODEL

REQUIREMENT ANALYSIS SPECIFICATIONS

SYSTEM DESIGN

IMPLEMENTATION AND UNIT TESTING

INTEGRATION AND SYSTEM TESTING

OPERATION AND MAINTENANCE

SYSTEM
OBJECTIVE

STUDY

PRELIMINARY SURVEY REQUIREMENT SPECIFICATIONS PERFORMANCE CRITERIA SYSTEM HARDWARE AND SOFTWARE REQUIRED System Study is to measure that how beneficial or practical the development of an information system will be to an organization. It is also known as the Feasibility study. Feasibility analysis is a cross life cycle activity, which has to be continuously performed throughout the system development. By using the creeping commitment approach, feasibility is measured at different times in the system development. This evaluation ensures that the project is beneficial and practical to an organization.

Feasibility Test: There are three categories of feasibility tests: 1. Operational Feasibility 2. Technical Feasibility 3. Economic Feasibility.

OPERATIONAL FEASIBILITY :- is how well the solution will work in the organization and how the end-users and managers feel about the system. This people oriented test measures the urgency of problem or the acceptability of a solution. i.e. Is the problem worth solving? PIECE is used as the basis for analyzing the urgency of problem or the effectiveness of a solution. PIECE stands for: P Performance I Information E Economics C Control E Efficiency

TECHNICAL FEASIBILTY centers around the existing computer system and to what extent it can support the proposed system. ECONOMICAL FEASIBILTY includes the cost benefit analysis. That is to determine whether the procedure to be applied is benefits and savings are expected from the candidate system.

Preliminary Survey The client already had a set system which was manual. This manual system was although efficient, but very time consuming and tedious. Also, the different modules were not fully integrated and needed an absolute understanding of the whole system to give the desired results. The main problems found out were bottlenecks at the user end because of slow data flow rate in a manual system. So, a preliminary survey was done check whether any simple modification could actually stimulate the system.

The present system seemed to be perfect if only data flow could be automated. The same modules could be implemented in the software.

Able to provide any information at any time. Proper relationship between tables should be maintained so that data integrity is maintained. Main module should have a password to avoid trespassing by unauthorized users.

Requirement Specifications The platform I used to develop my project "Tax Management System" is C+ +. During the development of this project I had several options of the platforms to use. After through study and discussion with my faculty and guide, I decided to use OOPS concept using C++ language. It acts as front end as well as back end. Back end deals with the file-handling concept of the C++. It is very easy and reliable platform as it is based on real world programming. It has very exciting features that are very similar to our world and life. These features are:-

Identity Classification Encapsulation Data abstraction Polymorphism Inheritance

All these features of C++ can run on any hardware or system that has 'Windows XP Professional' Operating System. It has many features and tools that will make our computing easy, effective and entertaining. For example, we can use remote desktop to access our work computer and its resources from home, as well as view fields and document on our computer's desktop from a co-worker's computer.

I developed my project in the OOPS environment using C++ language. OOPS stands for "Object Oriented Programming System". It is a way of design

software in which software is discrete collection of objects. As C++ is a structural programming, it is based on modularization. Object-oriented programming (OOP) is the most dramatic innovation in software development in the last decade. It ranks in importance with the development of the first higher-level languages at the dawn of the computer age. Sooner or later, every programmer will be affected by the object-oriented approach to program design. Our application area of the project will include all the tasks involving taxes and its numerical Functions (Fn).

Performance Criteria

After the initial investigation of the present system and the clients requirements some performance criteria were deduced. These criteria cover both the software (s/w) and the hardware (h/w) aspect of the project. System Hardware and Software Required

After knowing the performance criteria, it became fairly easy to decide on the hardware and software platform.

The next step was to decide which software to use in order to develop and support the system. This project requires the latest version of either the Microsoft or the Borland C++ compiler. Both products come in low-priced. The computer should have enough processor speed, memory, and hard disk space to run the complier we've chosen. I checked the manufacturer's specification to determine these requirements. They were found to be: Software Required RAM Operating Platform Hard Disk Processor : : : : : C++ Max 256 Mb Min 20 GB Pentium Series

Window XP

SYSTEM ANALYSIS
OVERALL STRATEGY PROBLEMS WITH THE CURRENT SYSTEM ADVANTAGES OF COMPUTERIZATION DATA FLOW ANALYSIS OF THE CURRENT SYSTEM System Analysis

The goal of the analysis stage is to build and understand the scenario involved and to create a description of just what is desired and what will eventually be built. To understand the problem we must have input to get output. This can take the form of interviews, specifications regarding to level of performance and random data. In order to have a structured approach to the analysis stage I had to choose a methodology to follow to have a complete analysis stage. The analysis stage is probably the most important as a mistake or missed requirement from analysis phase may cost much more time and money to fix later than if it had been caught in the analysis phase. Therefore it is imperative that at the analysis stage the best job possible is made. This section outlines the strategies followed in organizing the analysis phase.

Overall Strategy To understand the current processes for the feedback, I developed the following strategy: Sample all documents and records of information. Observe actual procedures followed. Determine the current strategies.

Problems With the Current System The current system is not organized. It is a system based on more of common sense. The main idea behind this system is as it has been going on fine. The speed of the system depends on human speed and mood. Since it is totally depending on human, efficiency is low. There is less security as all the information is basically kept as hard copy in a register. The computer back up is also in the file system. Advantages of Computerization Upon computerizing the present system, it will become an organized one. Efficiency will increase and so will data flow speed. Since it is a program (prog) on taxation, the security becomes a major issue with it ,so another advantage of computerization is security. Since main login process will have a password, unauthorized person will not be able to access any information.

Data Flow Analysis For The Current System

After completion of the deep study of the current system, I am now ready to do the data flow analysis of the client. This Data Flow Analysis consists of the Data Flow Diagrams (DFDs) which describe processes and data movement in the system and Data Dictionary (DD), which defines the systems elements. Both provide useful information for designing the candidate system.

SYSTEM DESIGN
DESIGN ANALYSIS ENTITY RELATIONSHIP DIAGRAM DATA DICTIONERY DATA FLOW DIAGRAM Design Analysis After understanding the business functions, purpose of the database, the performance needs of the application and the ease of maintenance, the designing part begins. A good design is the foundation to a correct, easily expandable and maintainable system. A maintainable system is one that is flexible and is simple to modify, if the system cannot adapt easily to the changing business environment, exceedingly efforts will be required to keep it serviceable. Design is a procedure for creating the blueprints for a system like the architects draft for the constructor to create the building. Entity Relationship Diagram

Entity-Relationship model is based on perception of real world as a collection of basic objects called entities and relationship among those objects. Entities are related by relationships between common information, where relationship at any point in time is an association between two entities. The ER diagram is a technique that is useful in the designing phase to represent this logical part of the database. Since the entities had been identified in the analysis stage the only process left to build an ER diagram is to represent the relations. Designing the ER diagram took several drafts before the final version was complete.

E_ID Ad d

Nam e A
P F

Basic Pay HRA

Ag e

CC A

A_Name A_Ad d

A_I D

Employee

Giv es Info

Accountant

gets

generates

Tax

amount tax

rebate

saving

The various concepts were included in the ER diagram

I.

ENTITIES Employee

Accountant

II.

ATTRIBUTES Add Age Basic Pay CCA E_ID HRA Name PF

For Employee Entity:

For Accountant Entity A_Add A_ID A_Name

III. RELATIONSHIP Gives Info(Information)

Data Flow Analysis For The Current System

After completion of the deep study of the current system, I am now ready to do the data flow analysis of the client. This Data Flow Analysis consists of the Data Flow Diagrams (DFDs) which describe processes and data movement in the system and Data Dictionary (DD), which defines the systems elements. Both provide useful information for designing the candidate system.

Data flow diagram (DFD) DFD or Data Flow Graphs are the cornerstone for structured systems analysis and design. It views the system as a collection of functions that transforms the inputs as desired outputs but does not go into the details of the transformation. This process modeling tool depicts flow of data through a system and processing work performed by the system. It has diagram of processes, data stores, data stores view, entities and data flows.

Although data can be organized in several ways: stored in data repositories flow in data flows transferred to and from the external environment

DFD is preferred here as it can be expressed by means of an attractive graphical notation that makes them easy to use and understand.

The four entities that must be represented are: Data flows

Used to connect process to each other, to source or sink. The symbol used is an arrow.

Data stores

The data repositories for data that is not moving. It is represented by one side open rectangular box.

Processes

Transforms of incoming data flow(s) to yield output data. The symbol used is a circle.

External entities

The sources or destinations outside the specified system boundary. The symbol used is a rectangle.

The DFDs for the current system is given here:

EMPLOYEE

TAXATIO N SYSTEM

ACCOUNTACY ACCOUNTANT

CONTEXT DIAGRAM

ZERO-LEVEL DFD

1.0
NEW RECORD UPDATE MASTER

ACCOUNTANT

ENTER
DETAILS EMP_MASTER

2.0
CALCULATE SALARY

REFER RECORD

UPDATE SALARY EMP_SALARY

3.0 EMPLOYEE
TAX CALCULATION

SALARY DETAILS

PAY SLIP

LEVEL 1 -DFD

Employee_master

1.1 Accountant Employe Name , E_id Enters Details Acknowledgment Employee

Leave_record

2.1 Basic Income HRA, Conveyance, Leave taken Annual Salary Output Employee

Employee_salary

Employee ID

Input Output

3.1 Taxable Income Income tax

LEVEL 2 -DFD

Form Details 1.1 Entry of Details

Valid

1.2 Processe s Info

AcknowledgmentEmployee

2.1 Employee ID

Invalid 2.2 Valid Taxable Income generate Employee

Entry Details

Data Dictionary

Simply putting data dictionary (DD) is data about data called metadata or description. It is a centralized collection of definitions of all data flowing among functions and to or from data stores. Data dictionary removes redundancy and inconsistencies. The Data Base Administrator (DBA) uses data dictionary in every phase of data base life cycle. The proposed Taxation Management System is designed in the next stage following the DFDs and the DD.

SYSTEM TESTING AND IMPLEMENTATION

 TESTING UNIT TESTING SYSTEM TESTING TEST CONCLUSION IMPLEMENTATION Testing Even completion of the design and coding stage does not imply that the development of the software is complete. The system designed needs to be verified so that errors dont creep in, although it is inevitable to develop a system without any errors. The project was under constant scrutiny to ensure that its implementation was not deviating from the original plan, and that functions that were implemented were doing their jobs correctly. The main functions of the system or user options on which testing were done can be summarized as follows: Retrieve an item detail from the database. Add a new items detail to the database. Generate detailed information about the issued items.

Each of these functions would need to ensure that they do only just what the user requests, and not something other than that. The system that has been implemented will need to stimulate typical situations that are currently being frequently performed manually at the home, as well as so typical ones.

As will explain later, these typical cases were tested more thoroughly than a typical one. The main objective of the testing is to show the presence of bugs, not the absence. No absolute certainty can be gained from the testing. The testing just ensures that the candidate system is an efficient alternative to the present system. The cautions kept in mind while choosing the tests are: 1. The testing should be based on sound and systematic techniques. 2. Testing should help locate errors, not just detect their presence. 3.Testing should be repeatable, i.e., repeating the same experiment, supplying the same input data to the same piece of code, produces the same result.

The tests done on the designed software was to verify the following properties of the software:

Correctness(satisfaction of the specifications) Reliability(how well it meets the requirements) Portability (running in different environments) Usability (ease with which user can use the software) Maintainability (modifications after initial release), etc.

Unit Testing Individual components are tested to ensure that they operate correctly. Unit testing treats each component as a stand-alone entity which does not need other components during the testing process. In my project, every single menu has been checked individually. The sheer advantage of unit testing is size of a small module is small enough that we can locate the error fairly.

System Testing System testing is actually a series of different tests whose primary purpose is to fully exercise the computer based system. The testing verifies that all elements mesh properly and that overall system function/performance is achieved. This testing is closet to everyday testing. During system testing, we evaluate a number of attributes of the software that are vital to the user.

LEVELS OF TESTING

UNIT TESTING

SYSTEM TESTING

Test conclusion

After all the tests on the designed software to verify its various qualities following conclusions were attained:

Correctness: The designed software meets the functional requirements specifications to a fair degree of correctness.

Reliability: Based on the test data, the client termed the software reliable.

Robustness: The various message and error codes enhanced the robustness of the software.

Implementation After the system was tested, it was found to be working properly and without the presence of bugs and errors. So it was time to implement the system on user level. The old system was changed and feasible requirement of both the hardware and software was fulfilled to accommodate the new system. The new system found its acceptance in the organization promising to deliver better output and speed than the previous system. The usability factor was satisfied as the client was able to understand and handle the system with ease. There was no interface problem faced by the end-user. The portability factor was also good as the system was able to work on more than one system as demanded by the user. Overall the program was a success as it was able to provide the expected outcome. Although the maintainability cost is expected to be low, but it depends to a large extent on the changing environment.

SCOPE OF THE PROJECT

The scope of this project is limited to the In-house users i.e. the system would be available to the people working in the company and the clients who have requested for it. The people who can avail this program will be limited because of security constraints. The right to access will be decided by Database Administrator and proper login and password will be authorized to the concerned users. The system will be used with all the transactions of the company, and i intend to improve it as the technology improves. At present details collected, maintained and inserted manually. After implementation of this project, record will be inserted and maintained technically. This will reduce manual work and improve quality and speed and facility will maintain the queue of all the records that are entered by the Tax Management. It will help the management to access the data and results as and when required.