ABSTRACT

Online taxation system handle basic organization operations such as import and export details etc. The project set out to develop an online taxation system. In order to achieve this, information on basic operations of a taxation organization. This was derived through interviews and questionnaires administered citizens who interact with the organization. Data was supplemented through a thorough review of organizations output forms. Use case diagrams, class diagrams entity relationship models and behavioral diagrams were the design techniques used. The system was developed using Adobe Dreamweaver CS5, while MySQL and WAMP Server 2.0. Tests were done on the areas of functionality, performance, integration and the environment. After a series of successful tests, an online taxation system was established..

Table of Contents
Table of Contents.............................................................................................iv iv

Chapter 1........................................................................................................ xii 1.1 Introduction.......................................................................................xii 1.2 Problem Statement................................................................................xii 1.3 Significance of Project............................................................................xii 1.4 Objectives ............................................................................................xiii 1.5 Justification............................................................................................xiii Chapter 2....................................................................................................... xiv 2.0 Literature Review...............................................................................xiv 2.0.1 Literature Search Plan.....................................................................xiv 2.0.2 Resources........................................................................................xv 2.0.3 Information search details...............................................................xv 2.0.4 Information search results...............................................................xv 2.0.5 Summary and analysis.....................................................................xv 2.0.6 Case study.......................................................................................xv Chapter 3..................................................................................................... xviii 3.0 Methodology.....................................................................................xviii 3.1 Research Methodology.....................................................................xviii 3.1.0 Research Design ...........................................................................xviii 3.1.1 Target Population ...........................................................................xix 3.1.2 Sample Size ....................................................................................xix 3.2 Feasibility Study ..................................................................................xix 3.2.1 Feasibility Study .............................................................................xix Chapter 4....................................................................................................... xxi 4.0 System Analysis....................................................................................xxi 4.1 Introduction ..........................................................................................xxi 4.1.1 Levels of Requirements......................................................................xxi v

.................................................................................................................. xxi 4.1.1.1 Business requirements.................................................................xxi 4.1.1.2 User requirements ......................................................................xxii 4.1.1.3 Software requirements ...............................................................xxii 4.2 Functional Requirements......................................................................xxii 4.2.1 Registration....................................................................................xxii 4.2.2 Log-in: ........................................................................................xxiii 4.2.3 Getting information.......................................................................xxiii 4.3 FUNCTIONAL REQUIREMENTS..............................................................xxiii 4.3.1 Availability.....................................................................................xxiii 4.3.2 Reliability......................................................................................xxiv 4.3.3 Usability .................................................................................xxiv 4.3.4 Effectiveness...........................................................................xxiv Chapter 5...................................................................................................... xxv System Design..........................................................................................xxv 5.1 Systems Development Methodology.....................................................xxv 5.2 Normalization.....................................................................................xxvii 5.2.1 1st Normal Form..........................................................................xxvii 5.2.2 2nd Normal Form.........................................................................xxvii 5.2.3 3rd Normal Form.........................................................................xxviii 5.3 Design Table Structure......................................................................xxviii 5.3.1 Administrator...............................................................................xxviii 5.3.2 Employees...................................................................................xxviii 5.3.3 User registration............................................................................xxix 5.3.4 Export Table..................................................................................xxix 5.3.5 Import Table..................................................................................xxix vi

5.3.6 Payment Table...............................................................................xxx 5.4 Design UML Diagrams..............................................................................xxx 5.4.1 Use Case Diagram................................................................................xxx 5.4 Design UML Diagrams..........................................................................xxxi 5.4.1 Use Case Diagram.........................................................................xxxi Shows flow of activities by users of the system while interacting with the system......................................................................................................... xxxi 5.4.2 Entity Relationship Diagram (ERD)...........................................xxxii 5.4.3 Sequence Diagram......................................................................xxxiii ...........................................................................xxxiv 5.4.4 Class Diagram.............................................................................xxxiv 5.5 Design Screen Shots...........................................................................xxxv 5.5.1 Homepage.................................................................................xxxviii 5.5.2 User Registration..............................................................................xl 5.5.3 User Login ...................................................................................xli

5.3.4 Imports............................................................................................xlii Chapter 6...................................................................................................... xliii Implementation and Testing......................................................................xliii 6.1 Description of development/ environment tools used...........................xliii 6.2 Main Functional Modules......................................................................xliii 6.2.1 Login Module..................................................................................xliii 6.2.2 Search Module................................................................................xliv 6.3 Sample test data and error handling.....................................................xliv 6.3.1 Unit (module testing):.....................................................................xliv Chapter 7....................................................................................................... xlv 7.0 Conclusion And Recommendations.......................................................xlvi 7.1 Conclusion ..........................................................................................xlvi vii

7.2 Achievements ......................................................................................xlvi 7.3 Problems..............................................................................................xlvi 7.4 Solution to the Problems.....................................................................xlvii 7.5 Future Works.......................................................................................xlvii 7.6 Recommendations...............................................................................xlvii References.............................................................................................. xlviii Appendices.................................................................................................xlix Appendix 2: Project Proposal .........................................................................li Appendix 3: Sample Codes...........................................................................liii

viii

ix

xi

Chapter 1
1.1 Introduction
CDF funds was brought by the government of Kenya in order to develop different constituencies. This is done by allocating specific funds to these constituencies each year. There is a concern by the citizens to know how these funds are being used in their constituencies and how there are being allocated and why they are given a specific amount. This calls for an introduction of system will allow for accurate record keeping and ease of information retrieval. Accountability will be ensured since all records of imports and exports will be available.

1.2 Problem Statement

After many years of centralized planning and past attempts at decentralisation that did not bear much fruit, CDF was expected to bring the much needed development to local communities and to address the regional inequalities brought about by partisan politics. The CDF is said to have mainly been used for purposes of social development and to undertake projects such as the construction of health centres, schools, rural roads, water and sanitation, police posts and cattle dips among others. The current system of operations is slow, tedious and not optimal in accuracy. Lack of accurate and up to date records of all projectss may lead to wrong information being used when need arises and the retrieval process may be quite cumbersome. The CDF system will ensure that all projects and funds allocated to such projects are being collected; It will have records of all its projects and its fundings. Any new project has to be registered before being offered services. A retrieval of all this operations will be made easy as the information will be saved in the database..

1.3 Significance of Project

An introduction of system will allow for accurate record keeping and ease of information retrieval. Accountability will be ensured since all records will be available and
xii

records of all projects . This will encourage transparency, customer satisfaction due to quick and efficient services and collection of the deserved revenue.

1.4 Objectives
To have organized records of all the organizations employees. To allow correct payment of tax of goods being imported/exported goods. To allow transparency in the operations of the organization.

1.5 Justification
The project will reduce the problems being faced by the organization thus more revenue due to appropriate and timely payment of taxes. The system will have a record of all taxpayers, this will ensure that all of them do pay and in the required amounts. Ease of payment of taxes due to introduction of online payments will reduce the size of queues at the organizations offices and will reduce travelling to and fro to specifically pay tax returns.

xiii

Chapter 2
2.0 Literature Review
Online taxation system relates to the maintenance of information Technologies within a business of providing quality services to tax payers and Kenya revenue authority. The greater tax collection operational success relies on IT, the greater the need to preserve those technologies. Online taxation system allows for the registration of payment of taxes online, checking for customs fee on imports and exports online and checking of client details online. Duties of Online taxation system allows the administrator to make sure that all the imports and exports charges and employee details are correct. Research at De monfort University is of the view that IT support is rapidly moving from merely supporting clients, to that of a more service-oriented system. A service-oriented system is one where continual system development is practiced [McBride] keeping the support system in line with any modifications made by the Enterprises.

2.0.1 Literature Search Plan

To carry out the literature review, the study and collection information thats related to the systems project was done, the topics that were studied are: Online taxations Database Authentication the internet

xiv

2.0.2 Resources
A lot of resources were used to accomplish the above topic areas. The internet resources were the main sources of gaining information. Others included books from the library and lecturers.

2.0.3 Information search details

Lecturers were consulted from the university and students to provide useful ideas. Internet-based research was carried out at university.

2.0.4 Information search results

Books: Linda Night &TheresiaSteinbach. System development methodologies for web enabled EBusiness M. Connolly & Carolyn E. Begg .Database Systems a Practical Approach to Design, Implementation and Management. Fourth edition. McGraw Hill.Database Systems Concepts. 5th Edition

2.0.5 Summary and analysis

Carry out the research was I little bit tricky, most information about Online taxation was got from the internet, and the journals too gave the researcher a bit on information that was really needed. It was found that actually Online Taxation is one of the most growing internet fields and indeed in the future most firms will have to engage in online taxations to increase their chances of being competitive worldwide. Due to the increase of bandwidth and internet speeds especially in Kenya has made online taxations reliable.

2.0.6 Case study

There are several Online taxation system that have been developed in the market today to tackle the problems surrounding tax collection. Most are aimed towards improving

xv

efficiency when performing revenue collection activities. Some of these systems collection include.
Online Filing and Payments

Online filing and payment system allows you to electronically file Form E-500, Sales and Use Tax Return, and the accompanying schedule Form E-536, Schedule of County Sales and Use Taxes. Monthly with Prepayment taxpayers are required to use the online filing and payment system.

What Are the Benefits?

It is convenient It's available 24 hours per day, 7 days a week with the exception of a scheduled maintenance period each Sunday from 4:00 a.m. to 12:00 p.m.. If you are paying by bank draft, you can select a future draft date.

It is easy For most tax types, the online screens are designed to look like the return. It is accurate Some of the online forms calculate the tax for you. It is free Paying by bank draft is free. It is safe The web site and the taxpayers data are secured with SSL (Secure Socket Layer) with at least 128-bit encryption. It is acknowledged You will receive an acknowledgement from the Department that your return and payment have been received.

2.0.6.2 Chilean Online Tax System

The Chilean online tax system was conceived and implemented using Oracle's internetbased technology. The first phase was simply to place taxpayer information online. This knowledge base included help-yourself data on the tax structure, corporate topics, guidelines and procedures. It was a small beginning, but straightaway taxpayers got used to the idea of finding information online rather than visiting their nearest office or phoning for a printed document. Foreign investors are also encouraged to use the SII Web site as a source of information.
xvi

2.0.6.3 Electronic Federal Tax Payment System (EFTPS)

The Electronic Federal Tax Payment System (EFTPS) is a free service from the U.S. Department of the Treasury. Since it began in 1996, millions of businesses, individuals, federal agencies, tax professionals, and payroll services have used EFTPS. All federal taxes can be paid using EFTPS. You can make payments via this Web site, a voice response system, or special channels designed for tax professionals, payroll services, and financial institutions. Quick, secure, and accurate, EFTPS is available by phone or online 24 hours a day, 7 days a week. You can schedule a business payment up to 120 days in advance or an individual payment up to 365 days in advance.

xvii

Chapter 3
3.0 Methodology
3.1 Research Methodology
This refers to the methods used during data collection of the user and system requirements as well as an analysis of the data collected. This is done so as to come up with system requirements specification.

Includes: The research design The target and sample population The sampling procedure and techniques Procedure for collection and analysis procedures

3.1.0 Research Design

An intensive case study of Online taxation system was conducted to determine the operations by a taxation organization to people and the quality of services according to the organizations customers . The study was able to establish the problems currently faced by people and these were used to develop a system that would effectively solve these problems.

xviii

3.1.1 Target Population

All the citizens that have once or many times interacted with the taxation organization in one way or another, formed the population of this research. In total, thirty members in different places were used in the data collection process.

3.1.2 Sample Size

Purposive sampling was used to determine the sample population. All people have in some way interacted with the taxation organization . The citizens who best understood how the system works were selected.

3.2 Feasibility Study

3.2.1 Feasibility Study

A study was done to determine whether the proposed online taxation system would be of any benefit to the client. The study was based on economic, technical and operational aspects of a feasibility study.

3.2.1.0 Economic Feasibility

The economic feasibility study was carried out in order to determine the cost of developing, operating and maintaining the proposed system and if it is economically viable in relation to return on investment i.e. whether the benefits of implementing the new system would outweigh the cost of its development. It was found that the system is feasible since the system will assure accuracy thus accountability and right returns to the organization.

3.2.1.1 Operational Feasibility

It was performed to determine whether the new system operations are acceptable to the users and whether the citizens were computer literate in order for them to be able to work with the system efficiently. Most of the citizens were found to be proficient with computer operating systems which are the basic requirement for one to be able to conveniently use the system. It was determined that the people who will be the major users of the system are
xix

computer literate and needed only introduction and a little guidance to the system so as to be able to work with it. It was found that the computer cyber assistants would give handy assistance to the users should need arise as they do to normal applications

3.2.1.2 Technical Feasibility

This was done to determine whether there are required hardware and software platforms to support the implementation of the new system. There are several computers in our country especially the cyber cafes, which have Internet connection and also have the required software and hardware necessary to run the system. This shows that the system already has a ready environment and thus reducing any effort of acquiring any new hardware and software products. With the availability of the required technical, economical and the operational requirements, the system is therefore viable and can be designed and implemented as planned.

xx

Chapter 4
4.0 System Analysis

4.1 Introduction
The user requirements of an online taxation System are the needs of the stakeholders who directly interact with the system The following categorizes the requirements into three categories as shown below:

User requirements:- why the project is being undertaken Business requirements: - What users can be able to do with the system. Software requirements:-What developer needs to develop the system.

4.1.1 Levels of Requirements

4.1.1.1 Business requirements

These requirements grow out of the vision for the product which, in turn, is driven by mission (or business) goals and objectives. The projects vision statement articulates a long-term view of what the project will accomplish for its users. It should include a statement of scope to clarify which capabilities are and which ones are not to be provided by the project. The business requirements are: 1. Get information from the system. 2. The administrator can manage imports and exports. Responsible for making any data changes in the system
xxi

4.1.1.2 User requirements

Defines the software requirements from the users point of view, describing the tasks users need to accomplish with the product and the quality requirements of the software from the users point of view. Users can be broadly defined to include not only the people who access the system but also inanimate users such as hardware devices, databases, and other systems. In the system most user requirements are articulated in their concept of operations document. What users can be able to do with the system.

Register in the system. To use the system resources a user has to log into the system .

Search for a specific good. One can search for details of a good. Its attributes will be shown on a table.

4.1.1.3 Software requirements

Detailed descriptions of all the functional and non-functional requirements that the software must fulfill to meet business and user needs. Nonfunctional requirements include software design constraints, external interfaces, and quality attributes such as performance, security, installation ability, availability, safety, reusability, and more. Software requirements, which are documented in a software requirements specification, establish an agreement between technical specialists and business managers on what the product must do.

4.2 Functional Requirements

The software requirements in order to accomplish this project were:

4.2.1 Registration
Users willing to use the services of the system can be able to register by giving valid details. The following are the details obtained from those users willing to register:
xxii

First name Last name Gender Email address Telephone number Id No

4.2.2 Log-in:
This will allow registered users to use the different services of the system by providing username and password. Administrator should also provide his username and password in order to log-in.

4.2.3 Getting information

After providing valid username and password, this feature allows users to look for any Good information. Good name Year of manufacture Tax to be charged

4.3 FUNCTIONAL REQUIREMENTS

4.3.1 Availability
The user should access the system at any place and at any time as long as theres an internet access.
xxiii

4.3.2 Reliability
The system shall be able to operate for a long period of time before encountering errors or problems.

4.3.3 Usability
The user interface is user friendly, that is, clear and easy to use

4.3.4 Effectiveness.
The system shall be in line with the operating standards of the organization

xxiv

Chapter 5
System Design 5.1 Systems Development Methodology
A system development methodology is a very formal and precise system development process that defines a set of activities, methods, best practices, deliverables, and automated tools that system developers and project managers are to use to develop and maintain information systems and software. A methodology is a formalized approach to implementing system development lifecycle. A methodology will always vary depending on whether the emphasis is on business or on the data that supports the business. In this system the waterfall model was used.

5.1.0 Waterfall Model:

A sequential software development process, in which progress flows through the phases of

Conception, Initiation, Analysis, Design (validation), Construction, Testing and maintenance. To follow the waterfall model, one proceeds from one phase to the next in a purely sequential manner. For example, one first completes requirements specification. When the requirements are fully completed, one proceeds to design.

Requirements Analysis

Analysis Stage Design Stage Coding And Implementatio n Testing, Installation and maintenance

xxv

Consists of the following phases of development: Requirements analysis: Involves gathering information about what the customer needs and defining, in the clearest possible terms, the problem that the product is expected to solve. Analysis: Includes understanding the customer's business context and constraints, the functions the product must perform, the performance levels it must adhere to, and the external systems it must be compatible with. Design: Involves defining the hardware and software architecture, components, modules, interfaces, and data to satisfy specified requirements. It involves defining the hardware and software architecture. This is also the stage at which user interface design is addressed, including issues relating to navigation and accessibility. Implementation: This step consists of actually constructing the product as per the design specification(s) developed in the previous step. Typically, this step is performed by a development team consisting of programmers, interface designers and other specialists, using tools such as compilers, debuggers, interpreters and media editors. Testing: In this stage, both individual components and the integrated whole are methodically verified to ensure that they are error-free and fully meet the requirements outlined in the first step. Defects, if found, are logged and feedback provided to the implementation team to enable correction. This is also the stage at which product documentation, such as a user manual, is prepared, reviewed and published. Installation: Involves preparing the system or product for installation and use at the customer site. Delivery may take place via the Internet or physical media, and the deliverable is typically tagged with a formal revision number to facilitate updates at a later date. Maintenance: Involves making modifications to the system or an individual component to alter attributes or improve performance. These modifications arise either due to change
xxvi

requests initiated by the customer, or defects uncovered during live use of the system. Typically, every change made to the product during the maintenance cycle is recorded and a new product release (called a "maintenance release" and exhibiting an updated revision number) is performed to enable the customer to gain the benefit of the update.

5.2 Normalization
Is a process by which you identify and correct inherent problems and complexities in your records. It can aslo be defined as a process of assigning attributes to entities.

5.2.1 1st Normal Form

Administator(Admin_Name,Admin_password) Employees(Employee_idno,Fistname, Lastname, Email, phone_no, department, job_title, residence) Useregistration(id_No,First_Name,Last_Name, othernames,email,password) Export(productid,productname,producttype,year_of_manufacture,custom_charge, exporting country) Import (productid,productname,producttype,year_of_manufacture,custom_charge, country_of_origin ) TaxPayment(Payment_No,Mode_of_Payment,user_name,email,phoneno, date_of_birth,residence)

5.2.2 2nd Normal Form

Administator(Admin_Name,Admin_password) Employees(Employee_idno,Fistname, Lastname, Email, phone_no, department, job_title) Useregistration(id_No,First_Name,Last_Name,email,password) Export(productid,productname,producttype,year_of_manufacture,custom_charge) Import (productid,productname,producttype,year_of_manufacture,custom_charge, country_of_origin )
xxvii

TaxPayment(Payment_No,Mode_of_Payment,user_name,email,phoneno,date_of_ birth)

5.2.3 3rd Normal Form

Administator(Admin_Name,Admin_password) Employees(Employee_idno,Fistname, Lastname, Email, phone_no, department, job_title) Useregistration(id_No,First_Name,Last_Name,email,password) Export(productid,productname,producttype,year_of_manufacture,custom_charge) Import (productid,productname,producttype,year_of_manufacture,custom_charge) TaxPayment(Payment_No,user_name,email,phoneno)

5.3 Design Table Structure 5.3.1 Administrator

This table captures administrator details

Table 1 Administrator table

5.3.2 Employees
This table captures employees personal details

xxviii

Table 2 Employees table

5.3.3 User registration

This table captures users personal details

Table 3 Users registration table

5.3.4 Export Table

This shows export details on items exported

Table 4 Export Table

5.3.5 Import Table

This shows export details on items imported
xxix

Table 5 Import Table

5.3.6 Payment Table

This shows tax payment details

Table 6 Payment table

5.4 Design UML Diagrams

5.4.1 Use Case Diagram Shows flow of activities by users of the system while interacting with the system.

xxx

5.4 Design UML Diagrams

5.4.1 Use Case Diagram

Shows flow of activities by users of the system while interacting with the system.

xxxi

5.4.2 Entity Relationship Diagram (ERD)

Shows relationships between objects in the system.

xxxii

5.4.3 Sequence Diagram

Sequence diagrams describe how objects interact over the course of time through an exchange of messages. A single sequence diagram often represents the flow of prods for a single use case.

Figure 3 Sequence Diagram

xxxiii

5.4.4 Class Diagram

The class diagram is core to object-oriented design. It describes the types of objects in the system and the static relationships between them.

Figure 4 Class Diagram

xxxiv

5.5 Design Screen Shots

xxxv

xxxvi

xxxvii

5.5.1 Homepage

Fig 5 Homepage

The homepage basically:

Welcomes the user to the website. Displays a login prompt that the user will use if they want to use the system. Displays the organizations motto. Web page links on the page:

Home Page Takes the user to the user login, this is where the user accesses the system.

Register This is where the user fills in their details before being registered as a user in the system. After registration the user can easily get any information from the system.
xxxviii

About Us Displays information pertaining to what the taxation system is about.

Contact Details Displays contact information pertaining to Steers restaurant.

xxxix

5.5.2 User Registration

Fig 6 User Registration

The user registration module displays all the registration details needed to be filled in so as to register into the system.

xl

5.5.3 User Login

Fig 7 Login

You can use the login module to prprod invalid access to the system. Only registered users can use the system. The administrator also has to login to use the system.

xli

5.3.4 Imports

Fig 8 Imports

Displays item information according to the details filled in the system. The user uses the search module to search a products name. All the details of that product is displayed in the table on the form.

xlii

Chapter 6

Implementation and Testing

6.1 Description of development/ environment tools used The development environment tools used to create this system included:

Windows 7 Ultimate This served as the operating system that the system ran on during its development life cycle. Adobe Dreamweaver CS5 for implementation of the design. This was used as a means of creating the interface, CSS style, connection to the database, designing and development of reports as well as well as creation of source code.

SQL is the software that was used in the creation and designing of the database and different tables in order to enable the system manipulate, store, save, update, delete and retrieve information/data from it.

WAMPServer5 version 2.0 as the SQL server, to enable the database management system to run, since SQL cannot function without a server running. Microsoft Word 2010 was used as a means of generating documentation for the entire project. Visual paradigm is application software that was used to generate the use case, class, behavioral diagrams, Logical Data Models and Entity Relationship Models for the systems documentation.

6.2 Main Functional Modules 6.2.1 Login Module

This deals with logging in the customer so that they can be able to access the system a for security purposes. This module was developed on both the user and administrators side of the system. The administrator has to log in as an administrator and a user as a user. This is achieved by the use of a username and a password.
xliii

6.2.2 Search Module

This allows access to information. On the user side, the user can find any goods details and on the admin side, the administrator can access employee detail.

6.3 Sample test data and error handling

The testing processes used during development of the system are as follows:

6.3.1 Unit (module testing):

In this case, each module is tested as a single program. A set of predetermined data is fed through the module and the output compared with the expected one.

6.3.2 Integration testing: The process of checking that the elements of the system
interact as specified in the system design specification

6.3.3 System testing: Testing the system as a whole to ensure that it meets the
requirements specified at the beginning of the project. It assesses the system on its functionalities, performance and soundness.

FIELD National ID no First name Last name Email

CORRECT DATA 279600 Sheila Chebet shishiling@ya hoo.com

WRONG DATA 23ABNH678 12345345 1234567 (null)

ERROR HANDLING Numbers only Letters only Letters only Email address is required

Password FIELD Name Password

578369 CORRECT DATA Sheila 578369

(null) WRONG DATA (null) 456789

Password is required ERROR HANDLING Username required Wrong password

xliv

Chapter 7

xlv

7.0 Conclusion And Recommendations

7.1 Conclusion The road towards completion of this system was rough though in the end of it all. The major
objectives set during the introduction have been achieved and I would like to congratulate all those people who have played part in the development of the system.

7.2 Achievements
The following are the key achievements made beginning from the data collection stage to analysis, design and implementation of the system as stated from the objectives stated earlier in the introductory part of this documentation:

Register and save users details successfully. Users are only able to access after registered onto the system. Only the administrator can make information changes that will be accessed by the users.

Being able to incorporate the two parties in my system successfully i.e. users, administrator. The great deal of implementing the database using different tables inform of queries was easier by use of simple software by the name SQL.

7.3 Problems
Time constraints whereby the project started late, consideration of other units as well as studying for April and August 2011 exams. The scope of the project was too large to cover the little time affordable. Since php was a new programming language to me, I had to learn everything from scratch. This was quite a heavy task considering the large amount of work to be covered. Finding a computer lab to code in was difficult, especially considering the huge number of students having lab sessions.
xlvi

 Some computers did not have the necessary software required to design the system.

7.4 Solution to the Problems

To deal with limited time, I had to forego some of my free time and sleep by working overtime. To deal with the inaccessibility to labs and lack of software in the labs, I had to use my personal computer at home, or borrow laptops from friends in order to be able to work form school. I had to rely a lot on the web, especially for the forum part of the project that required so much php code. I had to obtain some video tutorials on how to use Dreamweaver to perform some functionality.

7.5 Future Works

For future improvements, it is recommended that the scope be broadened to accommodate PIN generation, to handle tax payment through the internet. This will ensure that the entire organizations activities are covered, leading to better performance of the organization in general.

Time was an inhibiting factor in prproding the creation of a similar mobile-based

taxation system. It is recommended that a similar mobile system be developed to increase the usability of the system over a wider area as mobile phones will cover areas where the internet has yet to truly be a revolution.

7.6 Recommendations
The Online taxation system can be modified to support other services like online payments, PIN generation to make the system more effective.
xlvii

I recommend that people who may wish to modify this system in one way or another in future should keenly implement the following a functionalities to make the organizations operations more automated and better customer service.

References
1.Arthur M. Hughes. (1998), Strategic Database Marketing, Third Edition. 2.McGraw Hill (2005). Database Systems Concepts, 5th Edition Silberschatz, KorthandSudarshan. 3.M. Connolly, Carolyn E. Begg (2006). Database SystemsA Practical Approach to Design, Implementation and Management, Fourth edition. 4.William Stallings (November 16, 2005).Cryptography and Network Security Principles and Practices, FourthEdition.Prentice Hall publishing. 5.Linda Night, Theresia Steinbach, VinceKellen (November 2001). System development methodologies for web enabled E-Business: A Customization Paradigm.
6. .http://www.scribd.com/doc/5195326/PPT-on-SDLC-Models 2/21/2010 340pm

7. http://www.merttol.com/articles/web/web-site-development-life-cycle.html2/21/2010

340pm

8 .http://www.cs.cityu.edu.hk/~helena/cs34622000B/DBDesign.pdf2/21/2010 340pm

xlviii

9. Ann Navarro(2001) Effective Web Design(2nd Edition), Sybex Publishing 10. Berners-Lee(1999) Weaving the web designing the website, World Wide Web Consortium(W3C) Web design, www.dmxzone.com 11. Luke Welling and Laura Thomson(2001) Php and MySQL Web Development SAMS Publishing.

Appendices Appendix 1-Questionnaire:

xlix

Am carrying out a questionnaire about an online taxation system that am creating as my final project. Take your humble time to go through it and answer the following questions diligently, your views and time will be highly appreciated. Please check in the box provided. How often do you use the internet? Once a week Twice a week Frequently Have you heard of an online taxation system? Yes No Have you interacted with any before? Yes No If yes how was it ..

Would you want an online taxation system ? Yes No What are your thoughts if an taxation system was to be set up?
l

What features would you want included in an online taxation system? ........................................................................................................................ ...................................................................................................................................... ...................................................................................................................................... ............................................

Thank you very much.

Appendix 2: Project Proposal

Title Online taxation System
li

Introduction Having a manual system to handle all transactions and retrieval of information can be tedious and may lead to inaccuracies. The online taxation system will ensure easy information retrieval and accurate handling of information. This will be made possible by having an administrator handling all imports, exports, employee records and VAT. A user can easily search for information from the system by the use of search. To use the system both the user and the administrator have to log in. An introduction of system will allow for accurate record keeping and ease of information retrieval. Accountability will be ensured since all records of imports and exports will be available. Justification

The project will reduce the problems being faced by the organization thus more revenue due to appropriate payment of taxes. The system will have a record of all taxpayers, this will ensure that all of them do pay and in the required amounts. Objectives

To have organized records of all the organizations employees. To allow correct payment of tax of goods being imported/exported goods. To allow easy payment of taxes To allow transparency in the operations of the organization

Required resources Access to libraries Access to internet, Standard Pentium PC

lii

Windows XP SQL PHP Own computing facilities will be used to develop the system and preparing a report. Risks Locating relevant up to date literature Learning new technologies if they are required

Appendix 3: Sample Codes

Database connection <?php
liii

$conn= mysql_connect("localhost","root",""); mysql_select_db(taxationdb", $conn); if (!$conn){ die("not connected"); } ?> Imports Form
<?php session_start(); ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta name="keywords" content="" /> <meta name="description" content="" /> <meta http-equiv="content-type" content="text/html; charset=utf-8" /> <title>Prod Reservarion website</title> <link href="style.css" rel="stylesheet" type="text/css" media="screen" /> </head> <body> <?php $write=$_REQUEST['write']; $add=$_REQUEST['add']; $delete=$_REQUEST['delete']; function write() { $rems=$_SESSION['remagency']; $evntname=$_REQUEST['prodname']; $prodinfo=$_REQUEST['prodinfo']; require("connection.php");

liv

$insprod=mysql_query("insert into taxatationstbl set products='$pname', prodinfo='$prodinfo',agency='$rems';",$conn); if($insprod) { print"<font color='blue'><b>The Prod has been added</b></font>"; } } function add() { require("prodload.php"); } function delete() { require("connection.php"); $prods=$_REQUEST['prods']; $del=mysql_query("delete from prodstbl where prodss='$prods';",$conn) ; if($del) { print"<script language='javascript'>window.location = 'manageprods.php';</script>"; } } ?> <!-- end #header --> <div id="menu"> <ul> <li><a href="agentpages.php">View Searchs</a></li> <li><a href="manageprods.php">Manage upcomming prods</a></li> <li><a href="postpayment.php">Post Payment</a></li> </ul> </div> <!-- end #menu --> <div id="page"> <div id="page-bgtop"> lv

<div id="page-bgbtm"> <div id="content"> <div class="post"> <h2 class="title"><a href="#">Manage upcomming Prod</b></a> </td> </tr> </table> <table> <tr> <td> <?php if(isset($delete)) { delete(); } if(isset($add)) { add(); } if(isset($write)) { write(); } ?> </td> </tr> </table> </div> </div> <div class="post"> </div> <div style="clear: both;">&nbsp;</div> lvi

</div> <!-- end #content --> <div id="sidebar"> <ul> <li> </li> <br /><br /><br /><br /><br /><br /><br /><br /> <br /><br /> </ul> </div> <div style="clear: both;">&nbsp;</div> </div> </div> </div> </div> <div id="footer"> <p>Online Taxation system</p> </div> </body> </html>

lvii

lviii