He also said that he would like his database to consist of 4 tables, one for customer details, two for product details, and one for order details etc.
Information about end user’s computer
Fortunately, the end user already has a suitable computer system to enable him to use the database. The current system is an AMD Athlon 1500+ 512mb DDR pc2700 RAM, 40GB HDD, 40x CD re-writer, 3 ½ “ Floppy disk, 17” CRT Monitor.
He also has sufficient software, which is a bonus. Is current operating system is Windows XP professional and he also has office 2000.
Description of the previous system
Input of the previous system
At the moment the whole system is paper based. If a customer purchases an item, their details are written down on a little white card, this includes their name, address, telephone number etc and then it is stored into a filing case. Eddie then has to write out a receipt by hand and issue it to the customer.
If a customer requires delivery, there is an extra fee for postage and packaging and their information gets put into a separate file where at the end of the day it will be processed.
Process of the previous system
After the information is collected it is left. Hey don’t use it for anything else like advertising or sending special offers. It is just stored in a cupboard and every time a customer phones up or comes into the store and purchases a product it is taken back out and another card is filled in.
Output of the previous system
Again, the information is not used for output at all, the do not send special offers or print receipts. The receipts are all manually drawn up and written out. All products are paid for up front; no credit is given so there are no fines and no need to use the data for output.
Method used for the previous system
Data Flow Diagram of the previous system
Problems with previous System
Main problems with the previous system
Requirements of the new system
Objectives of the new system
Using access 2000 I will be creating a database for the company, this will make the system a lot better for my end user. To enable me to get an idea if what my end user actually wants he has filled in a questionnaire for me. This should help me understand fully what the end-user wants. My database will consist of four tables, each table representing different parts of the company.
The first table will be a table for the customer’s details, it will store the details of every customer that comes into the shop and purchases an item. It will store their name, address, telephone number and each one will have their own unique customer ID number. This information can then be used for any marketing schemes that my end-user comes up with and the data will be handy at all times.
My second table will contain information about the components that are available for the customers to purchase. It will consist of a list of the products that the shop has on sale and the type of that product. It will have the price, the amount that the business has in stock and a short description.
The third table will consist of a list of pre-built fully working systems that are on sale; it will have a field for system ID, the price, number in stock, and a specification of each computer system.
I will then have a fourth table consisting of information of the orders that have been placed, it will have the customers ID, the ID of the product that they have ordered, how much it will cost, and whether or not it need to be delivered.
How the objectives will be fulfilled
Description of the new system
Input of the new system
As I said above I will be putting the customer and product information details into the database using a mouse and a keyboard. I will be using a mouse to select to appropriate options and applications. I will also be using a VDU so I can actually see the information that I will be putting into the system.
Process of the new system
The process of the system is going to be pretty simple, I spoke with my end-use and we decided that I will make queries and sorts for the tables so that the information is easier to find and get hold of. We decided that it would be a good idea if I also include a mail merged letter so that things do not have to be written time after time.
Output of the new system
My end user has out the point across, that the output of the system is not really as vital as the input. The main purpose of creating this database is so that the details are stored safely on the computer. However a printer will probably be needed for the purpose of printing out records, and letters etc. This is not a permanent thing and maybe things will change later but for now this would be the only output.
Performance criteria and limitations of the proposed system
Qualitative
My database solution will enable the end user to be able to sort the customers surnames into alphabetical so that it makes it easier for the end user to be able to find a customers records.
My end user will also be able to sort the prices of everything that he sells into price order (for example cheapest to most expensive). This will make it easier for the end user, so that if he gets a customer asking about certain products that are on sale he can easily do a quick sort and be able to tell the customer.
Quantitative
With the solution I have made my end-user will be able to find the following:
- Begin using the database within 30 seconds of opening it.
- Find a customer using name or ID within 15 seconds.
- Find a certain product with information within 20 seconds.
- Find out if there re any deliveries that need to be made within 20 seconds.
System flow chart
Software and Hardware considerations
Hardware
The hardware that I will be using to create my database is as follows:
Computer system:
1.0Gghz Celeron Processor
256mb SD RAM
20gb HDD
Internal AGP SiS 8.0mb GFX card
15” Cathode Ray Tube (CRT) monitor – Sufficient size display so I can easily see what I am doing.
Keyboard – Standard RM keyboard enabling me to get the job done.
Mouse – 3 button Key Mouse to make selecting options easier.
Laser Printer – Printout copies of the work I am doing to take to my end-user to make sure it suits his needs accordingly.
Some of my project will have to be completed at home in my own time on my own computer; my own computer consists of:
AMD Athlon XP 1700+
768mb DDR PC2700 RAM
40gb HDD
NVIDIA Geforce4Ti 4800 SE
Creative Sound Blaster 5.1
Microsoft Intellimouse Explorer 3.0 Optical (USB)
Logitech Internet Navigator™ Keyboard Special Edition - Black
Software
The software that I will be using to create my database is as follows:
Microsoft Windows 98 SE Operating System
Microsoft Windows NT Network
Microsoft Office 2000:
Word
Access – Mainly using access because it enables me to perform complex searches, have a splash screen and create an advanced database system.
Excel
FrontPage
Outlook
The software that I have on my computer at home, which will allow me to be able to design the database, is:
Microsoft windows XP professional corporate edition
Microsoft Office XP:
Word
Access
Excel
FrontPage
Outlook
Data security of the new system
Use of passwords
I am going to be using a password for my database, as my end user has requested it. My end – user will need a password, to ensure customer confidentiality. The password will be a word requested by the end user and only he and his staff will have access to the password and therefore the database.
I have suggested that my end user should change his password on a regular basis, to ensure that if the password is found out it will get changed again. This makes the whole system more secure.
Also, to make sure that the system does not get infected by viruses I have also suggested that the end – user invest in some form of anti – virus software. The software I have suggested is Norton Anti – Virus 2003 but it is down to the end – users discretion whether or not he goes ahead with it.
Differences and similarities between the current system and the proposed ICT solution
Similarities
There are not many similarities between the two systems, as the general idea was to change the system to make it a lot better. However there is one similarity between the two systems, the same information is entered into the database as is entered onto cards. This is only a small similarity, as the whole process is completely different now.
Specification - Design
Possible solutions
There were a few other possible solutions to my end-users problem; I came up with a number of alternatives but the database solution just seemed to stand out as being the best. The other solutions that I came up with which were taken into consideration by my end-user were as follows:
- Swap the cards for sheets of paper, which could be stored in folder or filing cabinet. We decided that this would not be such a could idea, because its not really much of an improvement and my end-user needs a big improvement.
- A spreadsheet using Microsoft Excel. We also decided against because is not a very efficient programme for the type of thing my end-user wants. You cannot perform clear searches or have different tables etc.
- A table using Microsoft word. Again, we decided not to use word plainly because this programme is too simple and basic. It does not really include many advanced features like searches and the information cannot be stored neatly, which makes the information difficult to access.
Reasons and justifications for final choice of software and hardware
We eventually decided to go with the database using Microsoft Access, because overall we thought it was the best piece of software to use.
A few of the reasons why we chose Microsoft Access are:
- You can perform searches and queries
- Data is easily accessed
- Modern
- You can create tables which are linked together
- Create mail merged letters
- Password
In my hardware section I have already specified what I will be using for hardware. This specification of hardware is suitable for me to create the database because it offers enough speed and memory (both virtual and physical) to enable to be able to work efficiently. This is because the bigger the processor the bigger amount of RAM, all makes the computer a lot faster.
Outputs required by the end user
The outputs that are required by my end-user are:
- Invoices – So that the customer has a proof of purchases.
- Splash Screen – This is to improve the presentation of the database and to put information about the creator on.
- Reports – To enable the end user to print out hard copies of queries etc
- Mail-merged letters – So that the end user can automatically contact customers.
Inputs and stored data needed to create the outputs
Processes that are required to produce the required outputs
Knowledge and ability to use advanced package features
Relationships
The database that I will be creating will be a “many-to-many”. I will be in the form of first form normalisation. I will have four different tables, each having its own primary key that will be referentially integrated to a linking table, to make sure all the tables stay up to date.
My entities are linked to the linking table using primary keys to the foreign keys. To show that I have enforced the referential integrity I have used the following symbol:
.
Table structures
Validation procedures
Customer Details Table
My Customer Details table has the most validation procedures of all my tables. This is because it consists of a high number of fields and holds a high amount of information. My validation procedures for this table are:
-
First Name - >L<?????????????? This procedure means that when the user starts typing information into this field the first letter will always be a capital letter and the rest will be lower case. There is also a presence check on this field, which means that data must be entered into this field before moving on to the next.
-
Surname - >L<?????????????? This procedure means that when the user starts typing information into this field the first letter will always be a capital letter and the rest will be lower case. There is also a presence check on this field, which means that data must be entered into this field before moving on to the next.
-
Address 1 - There is a presence check on this field, which means that data must be entered into this field before moving on to the next.
-
Address 2 - There is a presence check on this field, which means that data must be entered into this field before moving on to the next.
-
Town – This field contains a Combo Box (drop down menu) so that the user is able to select a town from a drop down list of towns in the area. This makes is quicker to do than typing out the name of a town. If the town they are looking for is not in the list then the user is also able to type it in. There is also a presence check on this field, which means that data must be entered into this field before moving on to the next.
-
County - There is a presence check on this field, which means that data must be entered into this field before moving on to the next. This field also has a default value of “Kent” which means that “Kent” is always in this field unless changed.
-
Post Code - >LL00\ 0LL This procedure means that the user has to enter the data into the field in this format. So that means it has to be letter, letter, number, number \ number, letter, letter.
-
Telephone Number - \(99999") "999999;0;_ This procedure means that the information put into this field has to be put in, in this format.
Layout of screens and reports required as output
Reports
Proposed Test Plan
Implementation
Tables
Overview of tables
Here are all of the tables in my database.
Components Table
This table consists of the entire components on sale at E.J. Computers.
Design View (components table)
Here is my components table in design view. The fields of this table consist of Product ID, Type of Components, Name of Component, Price, Number of Components in Stock, and Description. It also consists of a primary key, which is the product ID. There is also a presence check for the Name of
Components field and the Price field.
Customer Details Table
Design View (Customer Details)
This is my Customer Details table in design view; it consists of 9 fields, which are Customer ID, First Name, Surname, Address 1, Address 2, Town, County, Postcode, and Telephone number. Customer ID is my Primary Key and its data type is auto number, the rest of the fields in this table are text fields.
Systems Table
This is the systems table; this table contains product information on every system for sale at E.J. Computers.
Design View (Systems Table)
Here is my systems table in design view; it consists of 6 fields, which are, System ID, Type of System, Name of System, Price, Number of Systems in stock, and Description. The System ID field is also the Primary Key for the table.
Orders Table
Here is my orders table; this table is designed to store all orders that are placed for E.J. Computers so they can keep records of outgoing orders and see which need delivery.
Design View (Orders Table)
Here is what my Orders table looks like in design view; it consists of 5 fields, which are Orders, Customer ID, Product ID, System ID, and Delivery. The Orders field is the Primary Key. This table was designed so that E.J Computers can keep track of outgoing orders
Testing
Evaluation
Evaluation Criteria and Success criteria
Performance Indicators
Limitations
User Guide
The user guide
Technical guide
Installation
Backup
Trouble shooting
