Creating a computer system.

Authors Avatar

TABLE OF CONTENTS

ANALYSIS        

The Company’s current system        

The Input, Output and Processing of the Current System        

What the new system has to do to satisfy the user’s requirements?        

The resource requirements        

Conclusion        

The final package for the system        

Overview of the System        

Explanation of Worksheets in the system        

Macros for each workbook        

Security        

Test Strategy        

Test Plan        

Test Data        

Schedule of Activities        

What Data Needs to be stored        


Analysis

Problem Statement

I have been asked to investigate a problem by Mr. and Mrs. Bains. I will develop a computerized system for Surinder and Pinder Bains who own an off license wine shop, called ‘The Wine Barrel’ on Victoria Street in Englefield Green. In their shop they sell various types of wine and alcohol. In addition to this they sell crisps, sweets and chocolates and non-alcoholic drinks. They have been running this wine shop for 15 years now.

When customer purchase goods from the wine barrel, they are given an invoice, (produced by hand) showing the totals of the goods bought. All invoices are written in a book by hand. The book contains carbon copies, so when they write invoices, they give the original to the customer, and keep the carbon copy of the invoice themselves. The business then keeps a copy of this invoice and files it away. At the end of each week, Mr. and Mrs. Bains count the invoice totals manually, to work out the total Gross Profit. They then add up their expenses, and work out the total Net profit received weekly and monthly.

The wine company may receive phone calls from customers, who may want large amounts of goods delivered to them. For these deliveries the business needs to write down customer names and addresses, again which they do manually, so they know where to deliver the goods. They keep the customer details in alphabetical order, in a card file. They write the customer details on index cards, and store them in a box under the till.

They manually update stock every few days, by either ringing up suppliers or going to cash and carries. They do not have a system which tells them how much stock they have left, or when they are running out of stock. Mr. Bains counts the stock that is running low, and writes down a list of stock, which needs re-ordering.  

The Systems Lifecycle

To properly solve this problem I will have to go through the following four stages of the systems lifecycle. I will break down the tasks into sub tasks. The first stage of the systems lifecycle is analysis.

  1. The analysis involves finding out the problem and finding out what the user requirements are.  It means I have to find out what the user wants the system to do and how it should work. To find this out I to have to research and plan questionnaires. I can also find out using your observation skills. I have to set out targets for myself according to what the user wants this system to do. When the information has been gathered then I can create an accurate design specification outlining everything the new system has to do.

When this stage is complete I can then proceed to the second stage of the System Life Cycle, which is Design

  1. During the design I am supposed to plan out the design of your system whilst trying to achieve the targets set out in the analysis. I will be required to generate a number of ideas relating each idea to the targets set out in the analysis. I will need to state how this design meets the targets and how they can be achieved.

I must take into account the structure of the current system and ways I can improve it. I must also take into account the current problems and the needs of the user(s). Then I will need to generate some ideas, considering the resources available. I will also need to justify the ideas. The design will include thorough testing strategy and plan. Upon completion of the Design stage I can then start the third stage of the System Life Cycle, Implementation.

  1. Implementation involves creating a system using the design specification and plan that was set out in the previous stage. When I have created my system I will also need to test my system. To check that it actually works and achieves the objectives set out in the analysis. I will also need to explain any changes I have to be made.

This will also involve creating a user guide, system flow chart, etc.

When I have finished the Implementation I can then go on to the last stage of the System Life Cycle, which is Evaluation

  1. Evaluation means that I have to evaluate the product commenting on if it meets the targets I set out in the analysis. I must ask myself if it meets the final specification that was draw up in the analysis and if it meets the user requirement. I also have to state if I have achieved what I set out to do. I also have to draw up some kind of conclusion talking about improvements I could make. If an electronic system was chosen I could use Microsoft access to design the system on or Sybase or even Oracle. Oracle would be a difficult system to use because it too advanced for me yet. A good system to choose would be Microsoft access because it gives you help, lets you set up tables, reports, queries, forms very easily. It is very simple to use as well. I must also comment on the approach and whether things were done efficiently.  

I have received feed back from my company, after giving questionnaires and observing Mr. and Mrs. Bains (see appendix). I interviewed both Mr. and Mrs. Bains individually. I went to do some observation at The Wine Barrel and I watched as the customers were being served. They wrote down the customer details on index cards.  I will now analyse the feedback from the interviews and observation.

The Company’s current system

The system that The Wine Barrel currently uses is a paper-based system, which they have been using for fifteen years. Whenever they need to add data they write it underneath the previous record. They store the data in alphabetical order. When they write down any names they write the surname first. They write down data on index cards, when they run out of space they would get new index cards to write on. On their system they record customer names, customer, telephone numbers, customer accounts and customer addresses so that they know where they have to deliver any wine purchased by the customers.

They also use their system to record what their customers have purchased and the total price. Their system is kept in a blue box underneath the till. When they want to delete data they either cross it out or tip-ex it. They haven’t got a backup copy of any of the data recorded on the system. If this system was lost or stolen the business would lose money and they would be in trouble, as it would expose their customer’s personal information. The owners of the shop, Mr. and Mrs. Bains usually enter the data into the system.

Join now!

Overall this system is very primitive and basic system, which can be easily lost. The good thing about this system is that data can be easily deleted even if it looks messy and data can be easily added. This disadvantage is that it might be difficult to read the writing afterwards and there is a greater chance of human error.  

All the invoices (produced by hand), which are given to the customers are copied, and filed in a ring binder for the business’s use. Invoices are written in a book containing carbon copies. When they write invoices, ...

This is a preview of the whole essay