www.arena.co.

ke 0713779527

DEVELOPING A PROJECT USING MICROSOFT ACCESS DATABASE

Case Study

Bukuma Information system

Due to your expertise and experience in system development, you have been hired to
be the head of Information Technology (IT) at Bukuma Limited, a company that runs
a supermarket. Your first task is to develop a computer based information system that
would ensure that:
1. Stock control & monitoring is efficient and effective.
2. Customers’ orders are processed accurately within the shortest time possible and
invoices sent in time.
3. Purchase orders are processed accurately in time to avoid delays in items delivery.
4. Data entry screens or forms are easy to use hence eliminating data entry errors.
5. Reports required by the management are generated within the shortest time
possible.
6. Communication between the branches is efficient.
7. Company data & information is secure from unauthorized users and only certain
company employees can access certain reports.
8. The overall operating cost is reduced by at least 40%.

By the end of the case study, we should have demonstrated how to:

1. Carry out the initial study.

2. Carry out fact-finding.
3. Define system hardware & software requirements.
4. Design a system using system & program flowcharts.
5. Construct a system that would allow:
(a) Inputting of data through forms.
(b) Updating, modification, and deletion of existing data.
(c) Carrying out of input validation and integrity checks.
(d) Search or filter specific records, query and retrieve specific records.
(e) Generate various transaction reports.
(f) Set up database security, menus and other startup options.
6. Come up with a good user manual.

Identification & definition of the problem.

The problem is to develop a computer-based transaction processing & stock control system that
would:
1. Input & process data about business transactions, e.g., data about products, orders, etc.
2. Produce output in form of Invoices, pay vouchers, etc

-1-
www.arena.co.ke 0713779527

3. Produce a variety of reports that are to be used for managerial purposes, e.g., inventory
levels, sales reports, payrolls, expenses, etc.
4. Carry out data maintenance, i.e., it should be able to update stored data.
5. Maintain the stock levels by automatically alerting the purchases department or the
management when the items go below the reorder level.
6. Produce reports, e.g., summary reports showing total sales by category, monthly product
sales & purchases reports.

The following project charter outlines the objectives, preliminary investigation report, and other
issues that will be considered before embarking on system development:

Project charter for Bukuma information system

Project name: Bukuma computerized information system
Team leader: Luis da silva, System analyst

Project objectives
The project development team will develop new computerized information system that will
support the operations of the company in order to realize the strategic vision for Bukuma products
sales and delivery of customer services. It is anticipated that, the new system will provide highly
integrated processes and services that will not only reach out directly to customers and suppliers
but also increase internal operational efficiency.
Therefore, improving of the current system can result in the following benefits:
1. Corporate profits will improved by 10% through reduction of bouncing orders.
2. It will ensure improved customer services by efficiently managing stock levels.
3. It will improve employees’ morale due to better processing and management of operations.
4. It will improve internal decision support so that decisions are more reliable & made on time.
5. Support the competitive strategy of the business.

Preliminary investigation
Preliminary investigation and feasibility study of the current manual & the proposed system was
done through:
1. Studying the organizational chart.
2. Quantifying work output against performance criteria.
3. Observing the behaviour of the employees.
4. Listening to external feedback from vendors, customers and suppliers.
By going through the investigative process, the team discovered the following problems with the
current manual system:
1. The constantly changing products presented to the market have created many internal
inefficiencies and customer services problems.
2. Increased customer base and sales through aggressive advertising may overload the current
system’s ability to process transactions.
3. Unpaid orders have increased from 4% only two years ago to 12%. The current credit
management system has to be improved.
4. Suppliers who have failed to deliver as per contracts have increased by 17% due to poor
procurement procedures.
5. Competition from other companies threatens the survival of the company unless there is a
change in management strategies.
6. Many orders are bouncing due to poor stock control. The orders that bounce are not given
priority when new stock arrives.
-2-
www.arena.co.ke 0713779527

7. The management is not exploiting the Internet as a marketing and service delivery channel.

Scope of the system

The proposed computerized system will support the following internal business functions:
1. Sales and customer order transaction processing.
2. Inventory control and procurement processing.

Recommendations for the new system

1. There is need to adopt automated data capture technology and methods, e.g., use of bar-
coding as a means of capturing product stock records and sales, which is an automatic
identification system currently being implemented in many modern business organizations.
2. Ensure that the order processing capacity of the unit is tripled by the end of fiscal year.
3. Reduce order response time by 50% by the end of fiscal year.
4. Provide improved marketing and promotion programs.
5. Improve any business processes, procedures and policies that have any visible impact on
member satisfaction and complaints.
6. Provide improved follow-up mechanisms for orders and backorders.

Feasibility of the proposed system

1. Schedule: The system would take 9 months to develop.
2. The technology required to develop the new system is readily available in the market.
3. The system users are happy with the proposal to develop the new system.
Cost benefit analysis
(a) Costs: The entire development and operational costs can be estimated as follows:
(i) Development - Ksh. 20,000,000
(ii) Monthly operational costs - Ksh. 1,000,000
(iii) Total lifetime of the new system - 5 yrs
Total lifetime costs = 20,000,000 + (12 x 1,000,000) x 5
= Ksh. 80,000,000
(b) Benefits:
(i) Profit from increased sales per month - Ksh. 100,000,000
(ii) Savings from introduction of paperless mail - Ksh. 1,000,000
(iii) Savings from reduced traveling costs - Ksh. 20,000,000
Total monthly benefits = Ksh. 121,000,000
Total lifetime benefits = (121,000,000 x 12 x 5)
= Ksh. 7,260,000,000
Conclusion
This report is intended to help the management to make decisions about undertaking the project.
Although the development of the new system seems expensive, it will contribute positively
towards corporate objectives when implemented in the future. It is cost-effective & beneficial to
the company because its benefits will greatly outweigh (undo) the costs by billions of shillings
throughout its operational lifetime.

-3-
www.arena.co.ke 0713779527

Fact finding
The members of the system development team have been given the responsibility to carry out a
detailed fact-finding activity through the following:
1. Documentations study.
2. Interviews.
3. Observation.
4. Questionnaires.

Documentations study
A number of manual documents were analysed. These include: Products catalogue, Invoices,
Purchase orders, sales reports, etc

Interviews
Various interviews were conducted which involved the management, employees in the company,
customers and suppliers.
For each of the Interviewee, an interview guide was used.
Below is a sample interview guide used with one of the staff at Bukuma distributors.

Interviewee name: _________________________ Interviewer: ______________________

Date: ______________________________________
Time: ______________________________________
Place: ______________________________________
Subject: _____________________________________
Time Interviewer Question or Objective Interviewee
Allocated Response
1 to 2 Objective - Open the interview.
min - Introduce ourselves
- Thank Mr. …… for his valuable time
State the purpose of the interview – to obtain policies on an existing
credit-checking system.
5 min Question 1:
What conditions determine whether a customer’s order is approved
for delivery?
Follow up
5 min Question 2:
What are the possible actions that might be taken once these
conditions have been evaluated?
Follow up
3 min Question 3:
How are customers notified when stock is unavailable for their
order?
Follow up
1 min Question 4:
After a new order is received, approximately how long does it take to
process it and put the order under shipment?
Follow up

-4-
www.arena.co.ke 0713779527

1 min Question 5:
Who are the individuals that perform the credit checks?
Follow up
1 to 3 Question 6:
min May I please have permission to interview all the people who carry
out credit checking?
Follow up
If so: When would be the best time to meet with each of them?
1 min Objective – Conclude the interview:
- Thank Mr. …… for his cooperation and assure him that he will
be receiving a copy of what transpired during the interview.
21 min Time allocated for base questions and objectives
9 min Time allocated for follow-up questions and redirection
30 min Total time allocated for interview (2.00 – 3.00 pm)

Questionnaires
In my preliminary investigation of the business operations, I decided to prepare some
questionnaires that would help me seek some classified information without the respondent
feeling threatened.
Below is an extract of one of the questionnaires used.

BUKUMA DISTRIBUTORS INFORMATION SYSTEM

Date: ………………………..

Introduction:
The IT department is in the process of developing a new information system. Please, take a
few minutes to fill in this questionnaire and return it to the IT office before ………… (date)
1. How often do customer orders bounce due to lack of enough stock?
Very often Often Not often Not at all

2. After receiving an order, how long does it take to process it from reception to date of
shipping?
I hour Several hours One day Many days

Fact finding summary & Recommendation report

A Fact-finding report gives a more detailed analysis of the existing system and proposals for
improving or overhauling it altogether.
The following is a layout outline of the report.

-5-
www.arena.co.ke 0713779527

Detailed system analysis report for Bukuma distributors

Current system: Manual system
Proposed system: Computerised model

1. Executive summary (about 2 pages)

(a) Recommendations
(b) Summary of problems, opportunities, and alternatives
(c) A Brief statement of objectives.
2. Background information (about 2 pages)
(a) Details of all the fact-finding methods used, e.g., interviews.
(b) Description of analytical techniques used.
3. The current system (about 5 pages)
Models of the current system in terms of:
(a) Data entry techniques, e.g., forms
(b) Files and data storage methods & media
(c) Information processing methods used.
Analysis of the current system in terms of: (about 5-10 pages)
(a) Performance, problems, causes and opportunities.
(b) Economic problems, causes and opportunities.
(c) Security and control problems, causes and opportunities.
(d) Efficiency and service problems, causes and opportunities.
4. Detailed recommendations (about 5-10 pages)
(a) Reasons why the current system should be improved.
(b) Limiting problems (recommendations)
(c) Proposed implementation plan for the new system:
(i) Scope and refinement.
(ii) Master plan.
(iii) Plan for the design phase.
5. Appendices
(a) System models.
(b) Any other appropriate documents.

System design phase

The design phase can be broken into two:
1. Preliminary design.
2. Detailed design.

Preliminary design
Preliminary design describes the functional capabilities of the proposed information system.
One of the tools that can be used at this stage to design the system is the System flowchart.

-6-
www.arena.co.ke 0713779527

1). System flowchart

The system flowchart shows a general overview of the functionality of the computerised
system.
The proposed system required for Bukuma distributors should be able to achieve the
following:
1. Input & process customer orders which may be in form of electronic messaging, post or
personal visit.
2. Produce output inform of reports that are used for managerial purposes, e.g., summary
reports showing total sales by category, purchase reports, inventory levels, pay vouchers,
sales reports & invoices.
3. Carry out data maintenance, i.e., it should be able to update stored data.
Bukuma distributors sales order processing system flowchart

Postal order Personal visit

Telephone/faxed
orders

Enter order
details

Is order No Display message

valid? “Invalid order”

Yes

Stock Access files

file

Update customer &

Customer Stock files
files

Delivery notes
Generate
reports
Invoices, payment
vouchers, etc

Sales report, Summary

Profit/loss statement report

-7-
www.arena.co.ke 0713779527

Detailed design
After designing the system flowchart, it possible to design the detailed designs for the various
system functionalities. These include:
1. Output design.
2. Input design.
3. Files and data stores design.
4. Hardware & software requirements.

Output design
This is the design of both screen and printed output.
The output requirements for Bukuma system include: Invoices, payment vouchers, and sales
reports.

Invoices
An invoice is produced after delivery of goods to a customer.

BUKUMA DISTRIBUTORS LTD

Industrial Area, Funzi Road Box 30307, Nairobi-Kenya
Phone: 257 – 020655147 Fax: 02065551418
Invoice

Bill To:
Company name _____________________________ Postal code ____________
Contact name _______________________________ Sent via _______________
Destination city _____________________________ Date due ______________
Country ___________________________________

Order number Customer name Order date Required date Date shipped

Product name Quantity Unit price Discount Amount

Subtotal
Freight cost
Total

Sales report
Sales report gives a summary of sales made within a period of time such as weekly, monthly or
annually.
Below is a sample sales report design.

BUKUMA DISTRIBUTORS LTD

Product sales for the year ____________
Category name ____________________

Order ID Customer name Product Amount

Total sales
-8-
www.arena.co.ke 0713779527

Payment voucher
A payment voucher is used to authorise payments to the suppliers.

BUKUMA DISTRIBUTORS LTD

Industrial Area, Funzi Road Box 30307, Nairobi-Kenya
Phone: 257 – 020655147 Fax: 02065551418
Voucher

Payment To:
Supplier name _________________________ Postal address_________________
Contact title ___________________________ Region ______________________
City _________________________________ Sent via _____________________
Country ______________________________

Purchase ID Supplier name Date ordered Date required Date received

Product ID Quantity delivered Purchase price Purchase discount Amount

Subtotal
Freight cost
Total

Input design
User interfaces in form of data entry forms or screens should be designed.
The forms for data entry should be clearly captioned, easy to use, attractive and consistent.
Some of the forms needed for Bukuma system are: invoice processing entry form, products entry
form, customer entry form, pay voucher processing entry form, suppliers entry form, and
transporters entry form.
Products entry form
It should allow the user to enter or view products. It has the following controls:
Product ID Quantity per unit
Product name Selling Price
Supplier Purchase Price
Category Unit in stock
Customers entry form
This is a columnar form with the following controls:
Customer ID Telephone
Company name Region
Contact name City
Contact title Country
Address
Invoice processing entry form
This is a compound form used to enter customer details in the main form and the items purchased
in the products subform:
-9-
www.arena.co.ke 0713779527

Customer name Destination name

Order number Date ordered
Contact name Date required
Title Date dispatched
Country Freight cost

Product name Unit price Quantity shipped Discount Amount

Pay voucher processing entry form

This is a compound form that allows the user to enter supplier’s details in the main form and the
items delivered in the products subform.

Company name Purchase Number

Contact Title Freight charges
Telephone Date ordered
Country Date received

Product name Unit price Quantity received Discount Amount

Suppliers entry form

It has two tabs; a company information tab & a Contact information tab.
Company Info tab Contact Info tab
Supplier ID Address
Company name Country
Contact name City
Contact title Region
Postal code
Telephone
Fax

Transporters entry form

Entry form for companies offering transport services to Bukuma may have the following
controls:
Freight Number
Company Name
Postal Address
Physical Address
Vessel Name
Phone

- 10 -
www.arena.co.ke 0713779527

Files and data stores design

There are two methods of data storage in a computer: Flat files and databases.
In Bukuma Distributors Information System, the database system is used. This will ensure that,
the following objectives are achieved:
1. There is sharing of data among the users of the system.
2. The data maintained is accurate & consistent.
3. Data is made available for current & future applications.
4. Easy access of data by the users.

Designing tables/file structures

This allows the system analyst to produce the data structure that will be used to store the data
elements in the system. In our system, we will use records to store data elements of the various
entities.
Before designing a file or a table structure, the following points but be considered:
1. The type of files to be constructed, i.e., is it a master, a transaction or a report file?
2. Method of data access in the file, i.e., it is random, sequential, or indexed sequential?
3. The size of the files & the storage media to be used.
Below are some of the file structures that will be designed for the Bukuma information system:

Table/file structures Elements

Inventory - Inventory number (PK)
- Inventory name
- Description
Products - Product number (PK) - Product name
- Quantity per unit - Unit price
- Quantity in stock - Purchase price
Customers - Customer number (PK) - Address
- Company name - City
- Contact name - Country
- Contact title
Supplier - Supplier number (PK) - Contact title
- Company name - Physical address
- Contact name
Purchase orders - Purchase number (PK)
- Product purchased
- Quantity purchased
Sales orders - Order number (PK) - Product ordered
- Customer name - Quantity
- Order date - Unit price
- Required date - Discount
Transporter - Transporter number (PK) - Postal address
- Company name - Phone
- Physical address

Entity relationship (E-R) diagrams

Some of the entities that may be used in constructing Bukuma distributors Information system
are categories, products, customers, employees, orders suppliers, transporters and purchase
orders.
Below is an E-R diagram for customers and the products ordered.

- 11 -
www.arena.co.ke 0713779527

Places Order Contains Product

Customer
1 1
Many Many

Interpretation:
One customer may place several orders, but each individual order can be placed by only one
customer (One-to-Many relationship).
Each order placed by a customer may contain many products (or, many products can be
contained in one order).

Hardware and software requirements

After studying the detailed system design specifications and recommendations, the management
of Bukuma decided to settle for a computer-based system.
Therefore, the hardware & software specialists in the development team visited various suppliers
in major towns and brought quotations and price lists for most of the required hardware &
software resources.
The table below gives a summary of the hardware requirements for Bukuma Distributors
information system.
Hardware facility Example Estimated cost (Ksh).
1. Computer IBM desktop computer
2. Storage media Optical disks, magnetic disks Documents collected
3. POS terminal Wand reader, magnetic card reader, bar-code from various suppliers’
equipments printer quotations
4. Printers Laser printer, Dot-matrix printer
5. Scanner
6. Others
The table below gives a summary of the software requirements for Bukuma Distributors
information system.
Software Example Estimated cost (Ksh).
1. GUI-based Ms-Windows 9x, 2000, Me, Xp; Mac OS9,
Operating system etc Documents collected
2. Application Ms-Office Suite, Lotus Suite, Corel from various suppliers’
programs WordPerfect Suite quotations
3. Antivirus software Norton Antivirus, MacAfee, AVG antivirus

Constructing Bukuma information system

Design database tables that are related to each other via Primary & foreign keys.

Table Primary /foreign key

Inventory - Inventory ID, ….
Products - Product number (PK), Sales ID (FK), Inventory ID (FK), ….
Customers - Customer number (PK), Company name, ….
Supplier - Supplier ID (PK), Company name (FK), …
Purchase orders - Purchase number (PK), Inventory ID (FK), Supplier ID (FK), …
Sales orders - Sales ID (PK), Customer name (FK), …
Transporter - Transporter number (PK), Supplier ID (FK), ….

- 12 -
www.arena.co.ke 0713779527

Entity relationship diagram for Bukuma database:

Categories Product Sales Order

Purchase Order
Customer

Supplier Transporter

Setting up integrity constraints

After setting up the database, integrity constraints such as Lookup fields & data integrity
constraints need to be set up in the database to enhance accuracy.
Creating a lookup field
A Lookup field displays a list of acceptable values that may be entered into a field. This prevents
entry of wrong data in a field.
NB: All foreign keys should be lookup fields.
To create a lookup field;
1. Open the table in Design view.
2. Select Lookup wizard in the Data Type column of the desired fields.
3. Complete the prompts in the lookup wizard.
When the table is displayed in datasheet form (data entry mode), select an item from the
drop-down list.
Data integrity constraints
These are rules that govern the entering, changing & deleting of data and records in a database.
The following are types of integrity constraints:
(a) Entity integrity constraint.
(b) Referential integrity.
(c) Domain integrity.
Entity integrity
These are rules that govern the composition of a primary key.
A primary key:
 Cannot contain a null value. A Null value is an empty space in a field that has no data.
 Must be unique.
 Does not allow duplicates.
Referential integrity
Referential integrity governs the nature of records in One-to-Many relationships between tables
in a database.
E.g., all foreign keys in the child table must have a matching record in the parent table.

- 13 -
www.arena.co.ke 0713779527

Referential integrity is implemented in 2 ways:

1. Restricted database – a restricted database will delete or update a parent record if there are no
matching child records.
A parent record is the one that has the primary key of the relationship, while a child record is
the one that has the foreign key of the relationship in the second table.
2. Cascaded database – a cascaded database will delete or update/change all matching child
records when the parent record is deleted or updated.
Note. To set referential integrity, display the Edit Relationships dialog box.
Domain integrity
In databases, the term domain is used to refer to the acceptable range of values an attribute can
have. This ensures that no field takes on a value outside the range of valid values.
For example;
In the Purchase Orders table, the date of items received is always less than or equal to the current
date.
This should be shown in the Validation Rule property box as: <=Now (). Now () is a function
that returns the current date.
In the Validation Text box, you can type; Date Received must not be in future.

Constructing data entry and user-interface forms

Forms are mainly created to reduce data entry errors.
Forms can be grouped into 2 main categories namely; primary forms and advanced forms.
(a) Primary forms
These are forms primarily used to enter data into underlying tables.
They include; customers, categories, employees, products, suppliers, transport & employees
details forms.
(b) Advanced forms
These are more complex forms that are based on underlying queries & unbound controls.
They provide the user with easy access to and manipulation of data in the underlying tables
& other database objects.
Creating the primary forms
The main factors to be considered in creating primary forms are:
1. The general form properties, e.g., record source (i.e., the underlying table).
2. Control properties for each of the objects.
3. Command buttons and their underlying event procedures and codes.
Customers form
This is a columnar form that draws its data from the customers table.
The form has command buttons Add Customers, Search, Close and Delete. These buttons are
brought to life by their underlying event procedures. The codes are generated using the
command button wizard that automatically starts when you draw a command button on the form.

Products form
This is a single columnar form. The text box controls are populated with data from the Products
table.
- 14 -
www.arena.co.ke 0713779527

To operate the form, three command buttons have been used; New Record, Close, & Delete.
Suppliers form
The form is designed using the Tab tool from the toolbox. The form is populated with data from
the Suppliers table.
The form has command buttons for adding a new record, closing a form, searching a record,
deleting a record. In addition, it has an Open Products Form button, brought to life by the
OpenForm wizard.

Transporter form
It is a single columnar form populated with data from the Transporter table.
The 3 command buttons are: Add New, Delete and Close.

User-Interface forms
These are forms that enable the user to access, manipulate, display, and print other forms and
reports.
In Bukuma system, the Main switchboard is used.

Creating reports
Reports are used to present information to system users.
The main features to be highlighted in creation of reports are:
1. General properties of the report, e.g., data source.
2. Control properties, grouping, and event procedures.
3. The report in design view.
4. Layout of the report needed.

Testing the system

Individual system modules were tested using test data and found to work accurately and
properly.
Sample test data and error messages that were encountered due to invalid data entry are given in
the Appendix of this project report.

Implementing the system

System implementation involves putting the new system into use.
The tasks carried out during the implementation stage are:
1. System management: - This involves installation, resource and staff allocation.
2. Staff training: - it is done without interfering with the business operations.
3. Security control and contingency planning: - in case the system breaks down.
4. Changing over from the old to the new system using the most appropriate method.
Evaluation report
Once the system has been installed, and is running, the programming team must evaluate the
system to ensure that it is working as expected.
The Evaluation report for Bukuma information system shows that, the following issues have
been addressed:
1. Out of stock problems have been addressed satisfactorily.
2. Stock transfer between warehouses is running smoothly.
3. Store managers, Accounts clerks, and order processing managers feel that they are in full
control of the system.

- 15 -
www.arena.co.ke 0713779527

The programming team has promised to address the minor emergent problems encountered
during the system maintenance phase.

Recommendation and conclusion

The new system received recommendation from all sectors of the organization after the first
month of operation.

User Manual
Below is a sample user manual aimed at helping the users of Bukuma information system.
Introduction
Bukuma information system is a computerized information system that enables users to process
business transactions more efficiently and accurately.
The system can help you prepare most of the documents that would otherwise take a lot of time
to prepare manually. Some of the documents include: Invoices, Pay vouchers, Sales reports,
Profit and Loss accounts, and many more.
Loading the system
To load the system:
1. Click the Start button, point to Programs, then click Bukuma System. A Log on dialog
box is displayed.
2. Enter your User name and Password, and then click OK.
The System main menu appears.
Menu descriptions
Within the Main menu, there are submenus that help the user to choose on the specific tasks to
process. These submenus are grouped into two:
1. Details processing submenus.
2. Viewing transaction reports.
You activate a submenu by clicking on its button.

Description of the submenu items.

a) Customers submenu
Once you click the Customers button, you will get the following items:
1. Customer entry and editing form.
2. Customer orders and invoice processing.
3. Preview and print invoices.
4. Preview and print a list of Bukuma customers.
b) Suppliers
This button displays the suppliers submenu with the options.
1. Entering new records, editing the supplier details and products supplied.
2. Processing purchase details for items below reorder level.
3. Preview and print a list of Bukuma suppliers.

Viewing transaction report submenus.

a) Sales reports
Clicking this button displays the sales dialog box from which you can select the report to
preview or print.
b) Purchase reports
Click this button to preview purchases made for each purchase order.
- 16 -
www.arena.co.ke 0713779527

Exiting from the program

To exit the program, simply click the Exit button located at the bottom of the main menu.

Troubleshooting data entry related errors

Any invalid or erroneous data you enter will result to error messages being displayed on the
screen.
Some of the error messages that you may encounter are:
Error message: The changes you requested to the table were not successful because they
would create duplicate values in the index, primary key or relationship.
Description: You are trying to enter the same item twice.
Solution: Avoid double entry.
Error message: The field Product ID cannot contain a null value because the required
property in the field is set to true.
Description: You are trying to proceed to another record or field yet you have not
selected the product name of the record.
Solution: Select the product before proceeding to the next record.
Error message: The value you entered isn’t valid for this field.
Description: You are trying to enter an invalid data type in the field, e.g., you are
entering text in a numeric field or an invalid date such as 46/32/2007.
Solution: Enter the correct data type.

Project appendix
Below is a sample appendix of the project report.
Test data used in Bukuma information system
Although a variety of test data was used to test each operation of the system, I have provided
only one test data table to prove that the system is properly functioning.

Products table
Product ID Product Name Description
1 Soda Beverages
3 Omo Washing powder for washing
4 Maize flour For Ugali
5 Milk Dairy product

- 17 -
www.arena.co.ke
- Compet 0713779527
ition
from
other Bibliography
companBelow is a list of books and reference materials used in developing Bukuma information system.
ies
threaten1. Dr. John Onunga.: Introduction to Microcomputers and Programming, Information Systems
s the Academy Ltd, 1997 & 2002.
survival
2. Jeffrey L.W. et el: System Analysis and Design Methods, McGraw-Hill, 2000.
of the
compan3. Mburu s., Chemwa G.: Longhorn Secondary Computer Studies Form 3, New Syllabus,
y Longhorn Publishers, 2005.
unless
4. Mburu s., Chemwa G.: Longhorn Secondary Computer Studies Form 4, New Syllabus,
there is
Longhorn Publishers, 2005.
a
change 5. Microsoft Access 2002: Northwind sample database, 1999.
in
manage 6. Saleemi N.A.: Systems Theory and Management Information Systems simplified, N.A
ment Saleemi, 1997 & 2000.
strategi 7. Sarah E.H, Glen J.C.: Microsoft Access 2000 Complete Edition, McGraw-Hill, 2000.
es.
- Many 8. Taylor G.: GCSE Computer Studies, Macmillan Press Limited, 1991.
orders 9. Williams BK: Using Information Technology: A practical introduction to computers and
are communications, IRWIN, 1995.
bouncin
g due to
poor
stock
control.
The
orders
that
bounce
are not
given
priority
when
new
stock
arrives.
- The
manage
ment is
not
exploiti
ng the
Internet
as a
marketi
ng and
service
deliver
y
channel
.

Scope of
the - 18 -

system