ONLINE TAX MANAGEMENT SYSTEM PROJECT REPORT
PROJECT REPORT
PROJECT SOURCE CODE
INDEX
1. Introduction:
Abstract
Company Profile
2. Synopsis
3. Requirement Analysis Document(RAD)
3.1
Introduction
3.1.1 Purpose Of The System
3.1.2 Scope Of The System
3.1.3 Acronyms And Abbreviations
3.2 Current
3.3 Proposed System
3.3.1 Overview
3.3.2
Functional Requirements
3.3.3 Nonfunctional Requirements
3.3.4 Pseudo Requirements
3.4 Functional Model
3.4.1 Scenarios
3.4.2 Use case Model
3.5 Object Model
3.5.1 Data Dictionary
3.5.2 Class Diagrams
3.6
Dynamic Model
3.6.1 Sequence Diagrams
4.
System Design Documentation(SDD)
4.1 Subsystem Decomposition
4.2 Persistent Data Management
5. Forms
5.1 Input Forms
5.2 Output Forms
6. Coding
7. Testing
7.1 Module Testing
8. Conclusion
9. Bibliography
ABSTRACT
The main aim of our project is to prepare a Tax summary or
Tax Returns of a client. In Tax Information system System, a client registers
himself enters all the details and uploads
various Documents that are necessary for preparation of Tax Summary and
Schedules for an interview after successful submission of all the documents. After all the
procedures are completed Tax Returns or Tax summary is prepared for all the
clients by the admin who calls the clients and arranges an interview for
discussing various issues regarding Tax summary
.
Once the client pays the
amount for preparation of Tax Summary he can download the PDF format of his Tax
Summary.
This project is composed of
two main modules which also includes many sub modules.
1.
Client module
2.
Admin module
Client Panel :
·
Register
·
Create client profile
·
Upload documents
·
Schedule interview
·
Tax Summary
·
Payment
·
PDF/Review/Correction
·
Authorization
·
E-File Acknowledgement
·
Refund Status
Admin Panel :
·
Call the clients
·
Collect Documents
·
Schedule interviews
·
Preview Client Profile and Documents
·
Interview
·
Tax Preparation
·
Send Tax summary
·
Tax Summary Queries
·
Review Tax Summary
·
Payment follow up
·
Payment Receipt
·
Discounts
·
PDF upload /Correction
·
Receiving E Files
·
Manual filling
·
Send E File
·
Refund Status
Client module includes
registration of clients, submission of various documents etc., Admin module
includes the calling the clients ,Scheduling interviews, Observation of various
documents and preparation of Tax Summary and sent a mail to the client upon
successful payment of fee.
The project has been planned
to be having the view of distributed architecture ,with centralized storage of
the database. The application for the storage of the data has been planned
.Using the construct of
MS-SQL Server 2005 and all
the users interfaces have been designed using the ASP.Net technologies .The
database connectivity is planned using the ‘SQL Connection’ methodology. The
statement of security and data protective mechanism have been given a big
choice for proper usage. The application takes care of different modules and
their associated reports, which are their associated reported ,which are
produced as per the applicable strategies and standards that are put forwarded
by the administrative staff.
REQUIREMENT ANALYSIS - ONLINE TAX MANAGEMENT SYSTEM PROJECT
3.1 INTRODUCTION
A
complete understanding of software requirement is essential to the success of
software development effort. No matter how well design/well coded, a poorly
analyzed and specified program will disappoint the user and bring the grief to
the user.
The
requirement analysis task is a process of discovery, refinement, modeling and
specification. The software initially established by the system engineer and
refined during software project, planning is refined in detail. Models of the
required information and control flow, operational and data content are
created. Alternative solutions are analyzed and allocation to various software
elements.
Requirements
analysis, software-engineering task that
bridge the gap between system level software allocation and software design
.Requirements analysis enables to specify software function and performance
indicates software’s interface with other system elements and established
design constraints that the software must meet. Requirement
analysis allows the software engineers to refine.
The
software allocation and build models of processes, date and behavioural domains
that will be treated by software designer with a representation of information
and function that can be translated to data, architectural and procedural
design. Finally, the requirement specification the developer and customer with
the means to access quality once the software is built.
3.1.1 PURPOSE OF THE SYSTEM:
The
main aim of our project is to prepare a
Tax summary or Tax Returns of a client. In Tax Information system System, a
client registers himself enters all the details and uploads various Documents that are necessary for preparation
of Tax Summary and Schedules for an interview after successful submission of all the documents. After all the
procedures are completed Tax Returns or Tax summary is prepared for all the
clients by the admin who calls the clients and arranges an interview for
discussing various issues regarding Tax summary
.Once the client pays the amount for preparation of Tax Summary he can
download the PDF format of his Tax Summary.
3.1.2 SCOPE OF THE SYSTEM:
Our system mainly focus on the Tax that need to be
paid by the people who are migrated from India
3.1.3 ACRONYMS AND ABBREVIATIONS:
The various acronyms and
abbreviations used in our project are
TIS : Tax information system
SSN : Social Security number
3.2 CURRENT SYSTEM:
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.
It is too expensive to
overlook the deductions that you are
entitled to ?
Let out professionals plan
and prepare your tax returns to make sure you get the maximum benefit you
deserve .
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
3.3 PROPOSED SYSTEM :
3.3.1 OVERVIEW
Why the new system?
With the new system the
following activities get more moment.
1. Login/Register
·
Returning clients should login to our website to update then profiles.
·
New clients should register at our website to create their profiles.
2. Documents
·
Upload / Fax your W2s, 1099 s or any other statement relating the
interest, divide or stocks.
3. Tax Interview
·
Schedule your convenient date time for brief Tax interview.
·
Keep all the tax relevant information ready for the Tax Interview.
4. Tax Summary
·
Tax Summary will be ready within 24 – 48 hrs after Tax Interview.
·
Login and check the Tax Summary.
5. Make Payment
·
Pay the Tax Preparation Fees at our website using pay pal Account or
credit card
6. Tax Returns
Download
·
Download Tax Returns in PDF on payment of Tax Preparation Fees.
·
Review Tax Returns carefully to ensure that there are no omissions if
misstatements.
·
Send us an Email or call us for any questions or corrections.
·
Sign the e- files authorization form and fax it.
7. E-File
·
We E-File your Tax Returns at no extra cost on receipt of
authorization.
·
Finally, check your filling and refund status at our website
3.3.2 FUNCTIONAL REQUIREMENTS - ONLINE TAX MANAGEMENT SYSTEM PROJECT
The system deals with Tax Information System
Module
description:
This project is composed of two main
modules which also includes
Many sub modules
1.
Client module
2.
Admin module
Client Panel :
·
Register
·
Create client profile
·
Upload documents
·
Schedule interview
·
Tax Summary
·
Payment
·
PDF/Review/Correction
·
Authorization
·
E-File Acknowledgement
·
Refund Status
Admin Panel :
·
Call the clients
·
Collect Documents
·
Schedule interviews
·
Preview Client Profile and Documents
·
Interview
·
Tax Preparation
·
Send Tax summary
·
Tax Summary Queries
·
Review Tax Summary
·
Payment follow up
·
Payment Receipt
·
Discounts
·
PDF upload /Correction
·
Receiving E Files
·
Manual filling
·
Send E File
·
Refund Status
Client module includes
registration of clients, submission of various documents etc., Admin module
includes the calling the clients ,Scheduling interviews, Observation of various
documents and preparation of Tax Summary and sent a mail to the client upon
successful payment of fee.
The project has been planned
to be having the view of distributed architecture ,with centralized storage of
the database. The application for the storage of the data has been planned
.Using the construct of
MS-SQL Server 2005 and all
the users interfaces have been designed using the ASP.Net technologies .The
database connectivity is planned using the ‘SQL Connection’ methodology. The
statement of security and data protective mechanism have been given a big
choice for proper usage. The application takes care of different modules and
their associated reports, which are their associated reported ,which are
produced as per the applicable strategies and standards that are put forwarded
by the administrative staff
3.3.3 NONFUNCTIONAL
REQUIREMENTS -
3.3.3.1 User Interface and Human
Factor :
The system provides user-friendly interface with both
Keyboard and mouse,
the forms are
§
Client Login form
§
Register form
§
Myprofile form
§ Spouse form
§ Dependent form
§ Bank information form
§ Vehicle information form
§ Documents form
§ Scheduled interview form
§ Change password form
§
Tax Summary form
§
Payments form
§
Tax return form
§
Admin login form
§
Register form
§
Assign Interviewer
3.3.3.2 DOCUMENTATION
§
Requirement Analysis Document (RAD)
§
System Design Document
§
Coding
§
Testing
3.3.3.3 HARDWARE CONSIDERATIONS
§
INTEL CELEON/P2/P4 : 600 MHZ OR ABOVE
§
RAM(SD/DDR)
: 256 OR ABOVE
§
HARD DISC
: 10GB OR ABOVE
§
PRINTER
: HP LASER JET
§
INTERFACE
: MOUSE, KEYBOARD
3.3.3.4 ERROR HANDLING AND EXTREAM
CONDITIONS:
The
users of the system either ADMIN or
CLIENT should
enter all the fields in the
relevant forms. The entered fields should
not
violate the primary key constraints. If the user either wants to
update or delete a record,
which is not in database, it will display
a massage.
3.3.3.5 SYSTEM MODIFICATIONS
number of extensions that the Client want to include.
3.3.4.1 Hardware requirement
§
486 Processor ( a Pentium based computer)
§
32MB of RAM
§
About 150MB of free Hard-Drive space
§
Windows NT Server 4.0, Windows NT Workstation 4.0 or
Windows98/Windows95 with TCP/IP Networking support properly installed and
configured.
§
A web server that supports ASP 2.0
§
A Database that supports ODBC
(Such as Microsoft Access or Microsoft SQL Server).
§
Microsoft Visual interDev 6.0
3.3.4.2 Software specifications
§ windows 2000 server/professional
ofr above
§ .Net Framework 2.0
§
Asp.Net, C# .Net
§
SQL Server 2005
§
IIS 5.0 or Above
MICROSOFT .NET FRAMEWORK
The .NET Framework is a new
computing platform that simplifies application development in the highly
distributed environment of the Internet.
The .NET Framework is designed to fulfill the following objectives.
·
To provide a consistent object-oriented programming environment whether
object code is stored and executed locally.
Executed locally but internet – distributed, or executed remotely.
·
To provide a code-execution environment that minimizes software
deployment and versioning conflicts.
·
To provide a code-execution environment that guarantees safe execution
of code, including code created by an unknown or semi-trusted third party.
·
To provide a code-execution environment that eliminates the performance
problems of scripted or interpreted environments.
·
To make the developer experience consistent across widely varying types
of application, such as Windows-based application and Web-based application.
·
To build all communication on industry standards to ensure that code
based on the .NET Framework can integrate with any other code.
The .NET Framework has two
main components; the common language runtime and the .NET Framework class
library. The common language runtime is
the foundation of the .NET Framework.
You can think of the runtime as an agent that manages code at execution
time, providing core services such as memory management, thread management, and
remoting,
while also enforcing strict
type safety and other forms of code accuracy that ensure security and
robustness. In fact, 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 class library, the other
main component of the .NET Framework, is a comprehensive, object-oriented
collection of reusable types that you can use 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.
For example, ASP.NET hosts
the runtime to provide a scalable, server-side environment for managed code.
ASP.NET works directly with the runtime to enable Web Forms applications and
XML Web services, both of which are discussed later in this topic.
Internet Explorer is an
example of an unmanaged application that hosts the runtime (in the form of a
MIME type extension). Using Internet Explorer to host the runtime enables you
to embed managed components or Windows Forms controls in HTML documents.
Hosting the runtime in this way makes managed mobile code (similar to
Microsoft® ActiveX® controls) possible, but with significant improvements that
only managed code can offer, such as semi-trusted execution and secure isolated
file storage.
ASP.NET
Server Application
Development
Server-side applications in
the managed world are implemented through runtime hosts. Unmanaged applications
host the common language runtime, which allows your custom managed code to
control the behavior of the server. This model provides you with all the
features of the common language runtime and class library while gaining the
performance and scalability of the host server.
The following illustration
shows a basic network schema with managed code running in different server
environments. Servers such as IIS and SQL Server can perform standard
operations while your application logic executes through the managed code.
Table and Index Architecture -
Overview
Fundamental
changes were made in table organization. This new organization allows the query
processor to make use of more nonclustered indexes, greatly improving performance
for decision support applications. The query optimizer has a wide set of
execution strategies and many of the optimization limitations of earlier
versions of SQL Server have been removed. In particular, SQL Server 7.0 is less
sensitive to index-selection issues, resulting in less tuning work.
Table Organization
The data
for each table is now stored in a collection of 8-KB data pages. Each data page
has a 96-byte header containing system information such as the ID of the table
that owns the page and pointers to the next and previous pages for pages linked
in a list. A row-offset table is at the end of the page. Data rows fill the
rest of the page.
SQL
Server 7.0 tables use one of two methods to organize their data pages:
§ Clustered
tables are tables that have a clustered index. The data rows are stored in
order based on the clustered index key. The data pages are linked in a doubly
linked list. The index is implemented as a b-tree index structure that supports
fast retrieval of the rows based on their clustered index key values.
§ Heaps are
tables that have no clustered index. There is no particular order to the
sequence of the data pages and the data pages are not linked in a linked list.
Table Indexes
A SQL
Server index is a structure associated with a table that speeds retrieval of
the rows in the table. An index contains keys built from one or more columns in
the table. These keys are stored in a structure that allows SQL Server to
quickly and efficiently find the row or rows associated with the key values.
This structure is called a heap. The two types of SQL Server indexes are
clustered and nonclustered indexes
Clustered Indexes
A
clustered index is one in which the order of the values in the index is the
same as the order of the data stored in the table.
The
clustered index contains a hierarchical tree. When searching for data based on
a clustered index value, SQL Server quickly isolates the page with the
specified value and then searches the page for the record or records with the
specified value. The lowest level, or leaf node, of the index tree is the page
that contains the data.
Nonclustered Indexes
A
nonclustered index is analogous to an index in a textbook. The data is stored
in one place; the index is stored in another, with pointers to the storage
location of the indexed items in the data. The lowest level, or leaf node, of a
nonclustered index is the Row Identifier of the index entry, which gives SQL
Server the location of the actual data row. The Row Identifier can have one of
two forms. If the table has a clustered index, the identifier of the row is the
clustered index key. If the table is a heap, the Row Identifier is the actual
location of the data row, indicated with a page number and offset on the page.
Therefore, a nonclustered index, in comparison with a clustered index, has an
extra level between the index structure and the data itself.
When SQL
Server searches for data based on a nonclustered index, it searches the index
for the specified value to obtain the location of the rows of data and then
retrieves the data from their storage locations. This makes nonclustered
indexes the optimal choice for exact-match queries.
Some
books contain multiple indexes. Since nonclustered indexes frequently store
clustered index keys as their pointers to data rows, it is important to keep
clustered index keys as small as possible.
SQL
Server supports up to 249 nonclustered indexes on each table. The nonclustered
indexes have a b-tree index structure similar to the one in clustered indexes.
The difference is that nonclustered indexes have no effect on the order of the
data rows. The collection of data pages for a heap is not affected if
nonclustered indexes are defined for the table.
Data Type Changes
Unicode Data
SQL
Server now supports Unicode data types, which makes it easier to store data in
multiple languages within one database by eliminating the problem of converting
characters and installing multiple code pages. Unicode stores character data
using two bytes for each character rather than one byte. There are 65,536
different bit patterns in two bytes, so Unicode can use one standard set of bit
patterns to encode each character in all languages, including languages such as
Chinese that have large numbers of characters. Many programming languages also
support Unicode data types.
The new
data types that support Unicode are ntext, nchar, and nvarchar. They are the
same as text, char, and varchar, except for the wider range of characters
supported and the increased storage space used.
Improved Data Storage
Data
storage flexibility is greatly improved with the expansion of the maximum
limits for char, varchar, binary, and varbinary data types to 8,000 bytes,
increased from 255 bytes. It is no longer necessary to use text and image data
types for data storage for anything but very large data values. The
Transact-SQL string functions also support these very long char and varchar
values, and the SUBSTRING function can be used to process text and image
columns. The handling of Nulls and empty strings has been improved. A new
unique identifier data type is provided for storing a globally unique
identifier (GUID).
Normalization
Normalization
is the concept of analyzing the “inherent” or normal relationships between the
various elements of a database. Data is normalized in different forms.
First
normal form:
Data is in first normal form if data of the tables is moved in to separate
tables where data in each table is of a similar type, giving each table a
primary key – a unique label or an identifier. This eliminates repeating groups
of data.
Second
normal form:
Involves taking out data that is only dependent on part of key.
Third
normal form:
Involves removing the transitive dependencies. This means getting rid of any
thing in the tables that doesn’t depend Solely on the primary key. Thus,
through normalization, effective data storage can be achieved eliminating
redundancies and repeating groups.
SQL
The
structured query language is used to manipulate data in the oracle database. It
is also called SEQUEL.
SQL *plus- the user – friendly interface:
SQL
*plus Is a superset of the standard SQL .it conforms to the standards of an SQL
– compliant language and it has some specific oracle add – ones, leading to its
name SQL and plus. SQL *plus was always called UFI
(user –friendly interface). The oracle server only understands statements
worded using SQL. Other front-end tools interact with the oracle database using
the SQL statements. Oracle’s implementation of SQL through SQL *plus is
compliant with ANSI (American
national standard institute) and the ISO (international standards organization)
standards. Almost all oracle tools support identical SQL syntax
Data can
be manipulated upon by using the Data Manipulation Language (DML). The DML statements provided by SQL are
select, update, and delete. SQL *plus 3.3 can be accessed only by giving the
valid username and password. This is one of the security features imposed by
oracle to restrict unauthorized data accessed. SQL allows provides commands for
creating new users, granting privileges etc.
All such
features of SQL*plus make it a power data access tool especially for oracle
products.
3.5.1 DATA DICTIONARY - ONLINE TAX MANAGEMENT SYSTEM PROJECT
TABLE NAME :
TAXREGISTRATION
FIELS
NAME DATATYPE
taxid varchar
fname varchar
mname varchar
lname varchar
phone int
userid varchar
pwd varchar
TABLE NAME :
ITINDEPENDENT
FIELS
NAME DATATYPE
taxid varchar
fname varchar
mname varchar
lname varchar
phone int
pedate datetime
vnumber int
vdate datetime
pbirth varchar
addressinp varchar
dateentryusa datetime
TABLE NAME :
ITINSPOUSE
FIELS
NAME DATATYPE
taxid varchar
fname varchar
mname varchar
lname varchar
phone int
pedate datetime
vnumber int
vdate datetime
pbirth varchar
addressinp varchar
dateentryusa datetime
TABLE NAME :
DOCUMENT
FIELS
NAME DATATYPE
taxid varchar
dtype varchar
dife varchar
status varchar
TABLE NAME :
SPOUSE
FIELS
NAME DATATYPE
taxid varchar
fname varchar
mname varchar
lname varchar
dob datetime
occupation varchar
ssnitin varchar
TABLE NAME :
DEPENDENT
FIELS
NAME DATATYPE
taxid varchar
fname varchar
mname varchar
lname varchar
relation varchar
other varchar
dob datetime
ssnitin varchar
noofyearsinusa int
TABLE NAME :
INTERVIEW
FIELS
NAME DATATYPE
userid varchar
pwd varchar
TABLE NAME :
VEHICLE
FIELS
NAME DATATYPE
make varchar
model varchar
pdate varchar
bmileage varchar
taxid varchar
TABLE NAME :
BANK
FIELS
NAME DATATYPE
bname varchar
anumber int
rnumber int
atype varchar
taxid varchar
TABLE NAME :
COMPOSE
FIELS
NAME DATATYPE
email varchar
subject varchar
attachments varchar
date datetime
body varchar
TABLE NAME :
PAYMENT
FIELS
NAME DATATYPE
taxid varchar
bank varchar
number int
expdate datetime
TABLE NAME :
SCHEDULE
FIELS
NAME DATATYPE
taxid varchar
sdate datetime
statusconfirmation varchar
assign varchar
TABLE NAME :
MYPROFILE
FIELS
NAME DATATYPE
taxid varchar
fname varchar
mname varchar
lname varchar
gendr varcha
dob datetime
ssninit int
address varchar
city varchar
state varchar
zip int
email varchar
TABLE
NAME :
ADMINMAIL
FIELS
NAME DATATYPE
sender varchar
receiver varchar
subject varchar
attachments varchar
body varchar
senddate datetime
TESTING - ONLINE TAX MANAGEMENT SYSTEM PROJECT
TEST
CASE NAME : ADMIN LOGIN
|
Description
|
Input
|
Expected
Output
|
Actual
Output
|
Remarks
|
|
User
name
Password
Password
|
Admin
****
****
|
Control
passes to password field
Control
passes to home page
Control passes to home page
|
Control
passes to password field
Control does not passes to home
page
Control passes to home page
|
pass
fail
pass
|
TEST
CASE NAME : CLIENT LOGIN
|
Description
|
Input
|
Expected
Output
|
Actual
Output
|
Remarks
|
|
User
name
Password
Password
|
Britle
****
****
|
Control
passes to password field
Control
passes to home page
Control passes to home page
|
Control
passes to password field
Control does not passes to
home page(user id does not matches with password)
Control passes to home page
|
pass
fail
pass
|
TEST CASE NAME : MYPROFILE
|
Description
|
Input
|
Expected
Output
|
Actual
Output
|
Remarks
|
|
Taxid
Fname
Mname
Lname
D.O.B
SSNtin
Address
City
State
Zip
|
Anil
Venkata
Anil
Kumar
5569
Andhra
Pradesh
500001
|
Control
passes to next field
Control
passes to next field
Control passes to next field
Control passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
|
Control
passes to next field
Control does not passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
|
pass
pass
pass
pass
pass
pass
pass
pass
pass
pass
|
|
Email
Occupation
Mstatus
Dependency
Ctype
Bank
Vehicle
Pnumber
Pexp
Vnumber
Vexp
|
anil123@gmail.com
Software
Engineer
yes
yes
New
yes
yes
B1758469
ID2879340554
|
Control passes to next
field
Control passes to next
field
Control goes to next page
Control goes to next page
Control goes to next page
Control goes to next page
Control goes to next page
Control passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
|
Control passes to next
field
Control passes to next
field
Control goes tonext page
Control goes to next page
Control goes to next page
Control goes to next page
Control goes to next page
Control passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
|
pass
pass
pass
pass
pass
pass
pass
pass
pass
pass
pass
|
TEST CASE NAME : BANK
|
Description
|
Input
|
Expected
Output
|
Actual
Output
|
Remarks
|
|
Bankname
Accountno
Routingno
|
SBI
SBI586
5894
|
Control
passes to next field
Control
passes to next field
Control passes to next field
|
Control
passes to next field
Control passes to next field
Control passes to next field
|
pass
pass
pass
|
TEST CASE NAME : VEHICLE
|
Description
|
Input
|
Expected
Output
|
Actual
Output
|
Remarks
|
|
Make
Model
Purchasedate
Beginning
mileage date
Ending mileage date
|
Ford
Fiesta
|
Control
passes to next field
Control
passes to next field
Control passes to next
field
Control passes to next
field
Control passes to next
field
|
Control
passes to next field
Control passes to next
field
Control passes to next
field
Control passes to next
field
Control passes to next
field
|
pass
pass
pass
pass
pass
|
TEST CASE NAME : CHANGE PASSWORD
|
Description
|
Input
|
Expected
Output
|
Actual
Output
|
Remarks
|
|
Old
password
New
password
Confirm
Password
|
*****
***
***
|
Control
passes to next field
Control
passes to next field
Control passes to next
field
|
Control
passes to next field
Control passes to next
field
Control passes to next
field
|
pass
pass
pass
|
TEST CASE NAME : PAYMENT
|
Description
|
Input
|
Expected
Output
|
Actual
Output
|
Remarks
|
|
Bank
number
Debit/Credit
number
Validity
Date
|
SBI435
JI259
|
Control
passes to next field
Control
passes to next field
Control passes to next
field
|
Control
passes to next field
Control passes to next
field
Control passes to next
field
|
pass
pass
pass
|
CONCLUSIONS AND RECOMMENDATIONS - ONLINE TAX MANAGEMENT SYSTEM PROJECT REPORT
The
entire project has been developed and deployed as per the requirements stated
by the user, it is found to be bug free as per the testing standards that are
implemented. Any specification-untraced
errors will be concentrated in the coming versions, which are planned to be
developed in near future. The system at present does not take care off the
money payment methods, as the consolidated constructs need SSL standards and
are critically to be initiated in the first face, the application of the credit
card transactions is applied as a developmental phase in the coming days. The
system needs more elaborative technicality for its inception and evolution.
No comments:
Post a Comment