computing final)

Upload: fusionet24

Post on 05-Apr-2018

221 views

Category:

Documents


0 download

TRANSCRIPT

  • 7/31/2019 Computing Final)

    1/127

    Computing Project Page 1

    Computing

    Project

    March 26th (Version 8 Final

    Draft)

    2012My project documentation including: Analysis, Investigation, Design,Testing, Software Development, Evidence of modification, UserDocumentation and EvaluationScott James Bell Producing a solution for Anchor Supplies

  • 7/31/2019 Computing Final)

    2/127

    Page 2

    Table of Contents

    DEFINITION OF TASK .................................................................................................................................... 5

    INTRODUCTION ...................................................................................................................................................................... 5

    DESCRIPTION OF BUSINESS .................................................................................................................................................. 5INITIAL BRIEF ........................................................................................................................................................................ 5

    BRIEF DESCRIPTION OF PROBLEM ..................................................................................................................................... 5

    BASIS FOR A PROJECT ............................................................................................................................................................ 5

    INVESTIGATION AND EXAMPLES OF CURRENT PROBLEM................................................................................... 5

    INVESTIGATION METHODS .................................................................................................................................................. 6

    INVESTIGATION OF CURRENT SYSTEM ............................................................................................................................... 6

    CURRENT SYSTEM FLOWCHART ...................................................................................................................................... 10

    DATA IN USE IN THE CURRENT SYSTEM ............................................................................................................ 12

    INTERVIEW ......................................................................................................................................................... 13

    INTERVIEW PLAN ............................................................................................................................................................... 13QUESTIONS AND RESPONSES: ........................................................................................................................................... 13

    INITIAL INTERVIEW RESULTS .......................................................................................................................................... 14

    END USER SURVEY ............................................................................................................................................................. 16

    SELECT END USER(S): ....................................................................................................................................................... 16

    ANALYSES OF INVESTIGATION .......................................................................................................................................... 17

    INITIAL RESEARCH ............................................................................................................................................................. 17

    POTENTIAL SOLUTIONS ..................................................................................................................................... 18

    MY SOLUTION...................................................................................................................................................................... 18

    ADVANTAGES: ..................................................................................................................................................................... 18

    BESPOKE SOLUTION ........................................................................................................................................................... 18ADVANTAGES: ..................................................................................................................................................................... 18

    DISADVANTAGES: ............................................................................................................................................................... 18

    CURRENT SYSTEM............................................................................................................................................................... 18

    ADVANTAGES: ..................................................................................................................................................................... 18

    DISADVANTAGES: ............................................................................................................................................................... 19

    GENERIC SOLUTION (MICROSOFT ACCESS) ................................................................................................................... 19

    ADVANTAGES: ..................................................................................................................................................................... 19

    DISADVANTAGES: ............................................................................................................................................................... 19

    END REQUIREMENT SPECIFICATION................................................................................................................. 19

    REQUIREMENT SPECIFICATION ......................................................................................................................... 21

    DESIGN .............................................................................................................................................................. 25

    SYSTEM OBJECTIVES .......................................................................................................................................... 25

    INPUT,OUTPUT,REPORTS AND OTHER DESIGN ELEMENTS.......................................................................... 27

    DATA INPUTS ..................................................................................................................................................... 27

    DATA OUTPUTS.................................................................................................................................................. 27

    PROCESSES.......................................................................................................................................................... 27

    DATA FLOW DIAGRAMS OF SYSTEM ................................................................................................................. 28

    CONTEXT DIAGRAM ........................................................................................................................................................... 28

    DRAFT:DATA FLOW DIAGRAM (LEVEL 0) .................................................................................................................... 29DATA FLOW DIAGRAMS LEVEL 0: ................................................................................................................................... 30

  • 7/31/2019 Computing Final)

    3/127

    Page 3

    DATA FLOW DIAGRAM LEVEL 1 ...................................................................................................................................... 31

    DESIGNS FOR INPUT SCREENS,OUTPUT SCREENS AND REPORTS.................................................................. 32

    MENU ................................................................................................................................................................................... 32

    STOCK ITEM INPUT ............................................................................................................................................................ 32

    STOCK ITEM SEARCHING ................................................................................................................................................... 32

    SUPPLIER ITEM INPUT....................................................................................................................................................... 32

    SUPPLIERS SEARCH ............................................................................................................................................................ 32

    - ............................................................................................................................................................................................. 33

    EXPORTING .......................................................................................................................................................................... 33

    PASSWORD MANAGEMENT............................................................................................................................................... 33

    POTENTIAL PROBLEMS REPLACING THE OLD SYSTEM..................................................................................... 35

    FILE AND DATA STRUCTURE ............................................................................................................................. 36

    RECORD SIZE ESTIMATION ............................................................................................................................................... 37

    MOCKUSER INTERFACE..................................................................................................................................... 38

    ALGORITHMS....................................................................................................................................................................... 45

    PSEUDO CODE...................................................................................................................................................................... 45

    ALGORITHMS &DATA TESTING....................................................................................................................................... 47

    TEST STRATEGY................................................................................................................................................. 52

    QUANTATIVE TESTING STRATEGY.................................................................................................................................. 52

    TEST PLAN........................................................................................................................................................................... 52

    SOFTWARE DEVELOPMENT ...................................................................................................................... 55

    EVIDENCE OF COMPONENTS AND SYSTEM BEING DEVELOPED........................................................................ 55

    WHITE BOX TESTING.......................................................................................................................................... 58

    FAILED CODING .................................................................................................................................................. 58

    USER INTERFACE TESTING................................................................................................................................. 60

    ERROR MESSAGE (FIGURE 1) ........................................................................................................................................... 70

    LOGICAL &RESPONSE TESTING ....................................................................................................................................... 72

    ERROR MESSAGES ......................................................................................................................................... 76

    MESSAGE REASON ......................................................................................................................................... 76

    ERROR ............................................................................................................................................................... 76

    EVIDENCE OF MODIFICATION ............................................................................................................................ 78

    USER DOCUMENTATION ............................................................................................................................. 79

    SYSTEM REQUIREMENTS ................................................................................................................................... 79

    INSTALLATION &START UP.............................................................................................................................. 80

    INSTALLATION.................................................................................................................................................... 80

    START UP............................................................................................................................................................ 82

    TYPICAL USE....................................................................................................................................................... 84

    MENU ................................................................................................................................................................................... 84

    ADD ITEM ............................................................................................................................................................................ 86

    ADDING SUPPLIER .............................................................................................................................................................. 87

    STOCK SEARCH.................................................................................................................................................................... 88

  • 7/31/2019 Computing Final)

    4/127

    Page 4

    SUPPLIER SEARCH .............................................................................................................................................................. 89

    BACK UP .............................................................................................................................................................. 92

    TROUBLESHOOTING........................................................................................................................................... 94

    GLOSSARY........................................................................................................................................................... 95

    SUPPORT............................................................................................................................................................. 95

    EVALUATION .................................................................................................................................................. 97

    PROBLEMS AND LIMITATIONS WHEN CREATING THE SYSTEM ............................................................................... 100

    GOOD AND BAD POINTS OF THE SYSTEM .................................................................................................................... 100

    END USER REPORT .......................................................................................................................................................... 101

    EVALUATION OF END USERS REPORT .......................................................................................................................... 103

    CONCLUSION...................................................................................................................................................................... 104

    APPENDIX ..................................................................................................................................................... 105

    MENU FORM...................................................................................................................................................................... 105ADD SUPPLIER FORM....................................................................................................................................................... 117

    ADD STOCK ITEM FORM .................................................................................................................................................. 118

    SUPPLIER SEARCH ............................................................................................................................................................ 119

    STOCK SEARCH.................................................................................................................................................................. 121

    EXPORTING FORM ............................................................................................................................................................ 121

  • 7/31/2019 Computing Final)

    5/127

    Page 5

    Definition of Task

    IntroductionFor this A2 Project Im developing a stock recording solution for Anchor Supplies limited. I

    discovered the client had a problem after investigating the clients websites

    online and contacted them asking if they had any problems that would could

    possibly be solved. The client (Mr T Hedges) has requested to develop a

    solution for the problem of stock level recording and management. We shall

    accurately define the problem so that we can create a tailored solution that

    meets the system/user requirements.

    Description of business

    My client Anchor Supplies provides Army and Surplus stock to customers around the world. They

    have a busy company with a large warehouse that stores their stock. Self described as Anchor

    SuppliesLtd, Europes Leading Genuine Government Surplus Supplier. They provide second hand

    and spare stock to large companies, military installations and charities around the world.

    Initial Brief

    My client wants a fully functioning stock solution to track and order their products. They want

    something to easily manage their stock and trading system that can help optimise their products and

    sales. My client believes themselves to have many problems which effects there daily operations and

    productivity.

    Brief Description of Problem

    My clients ordering process consists of the customer requesting stock items and them doing a

    manual count of the currents stock level. If they have enough stock then they provide it to the

    customer at an agreed price. However, if they dont have the appropriate stock level required by the

    customer they search their invoice tray and sticky notes to find contact details for the supplies. This

    leads to problems such as lost sticky notes and information.

    Basis for a project

    I have found some areas of development to create a foundation for a project that could solve my

    clients problem. I have decided to investigate the problem, examine the current methods and try to

    create a specification for the users requirements.

    I obtained the above information from the client and contacted him asking for the initial brief.

    Investigation and examples of current problem

    The current problem facing my client is that they dont have a current stock system and cant keep

    track of stock levels/ products.

  • 7/31/2019 Computing Final)

    6/127

    Page 6

    Investigation Methods

    I shall use the following methods for my investigation of the problem that faces my client:

    - Investigation of current system and form a basis for questions to ask the client- Interviews with my client on his requirements and with each evolution of the design stage- A sample of users that shall be using the end product (End Users) (Using Survey Monkey)- Questions on the current solution- Research into available solutions/technologies

    Investigation of current system

    I have compiled evidence below of their current data flows with in the company when ordering an

    item.

    First I decided to query their team for a stock check on some unpopular products in order to test

    their current system. This is there website with their contact details. I called and placed an fake

    order.

  • 7/31/2019 Computing Final)

    7/127

    Page 7

    I observed the data flow of items being ordered, stock levels being checked and the process of

    contacting suppliers. Below is a flow diagram of the processes I observed in the company. As you can

    see the stock request is a simple process but there decision option of contacting the supplier caused

    the staff problems, as they had to locate the suppliers information from an unorganised invoice

    tray.

    Below is a sticky note that is from the current system. This is supplier information and could easily

    be lost in the current system.

    Transcript: Item Name: Watches, Stock Level: +25, Supplier: Royal Watch Company LTD. Purchased:

    21st

    May 2011. Reference: 2127. Contact No: 01977678951. This shows the current data in use in

    the current system.

    Below is a sticky note that is from the current system. This is a request for supplier information.

  • 7/31/2019 Computing Final)

    8/127

    Page 8

    Transcript: Find money required For New Orders From Watch. Find Supplier. This is a process in the

    currents system as request to find the information.

    Below is a sticky note that is from the current system. This is a example stock request.

    Transcript: Item Name: Jeep, Stock Level: 1. Contact no: 01977 627191 (Outside the scope of my

    initial brief) Postcode: WF10 3QR (Outside the scope of my initial brief), Purchase price: 7900, and a

    request for who they purchased it from for stock replenishment.

  • 7/31/2019 Computing Final)

    9/127

    Page 9

    Below is a sticky note that is from the current system. This is a example of assorted information.

    Transcript: Account Details: Supplier Name: Armtech IT Services, Customer No: 29621, Reference:

    29621, Contact Details: 01924 767591, [email protected].

    The issue I can see with this system is that the sticky notes could easily be lost and they arent

    searchable very easily as theyre stored in a miscellaneous order slowing down the clients. Item

    information appears to be: Item Name, Item Description, Quantity and Price and Supplier

    Information is: Supplier Names, Supplier contact details, Supplier assorted information and supplieraddress. The information is also not stored well as unrelated information is stored in each sticky

    note and redundant information is present in the current system. Issues to raise with client:

    - Searchablity of information- Easily lost sticky notes- Redundant/irrelevant data- Current data stores- Attributes to store about items and supplier

  • 7/31/2019 Computing Final)

    10/127

    Page 10

    Current System Flowchart

    NoYes

  • 7/31/2019 Computing Final)

    11/127

    Page 11

  • 7/31/2019 Computing Final)

    12/127

    Computing Project Page 12

    Data in use in the current System

    Below is a table of information for the current system, Ive collected some attributes that are currently stored in the system so that I have some reference

    and information to show the client to accurately define what needs to be stored in the solution.

    Record

    no

    Record

    Name

    Data Type Range Example Data Description Validation Data Store

    1 Item Name Text N/A MarshMallows The Products name N/A Post it Note/Users

    Mind

    3 Purchase

    Price

    Decimal 1-5 12.79 The price of the Product

    as its currently being

    sold

    N/A Invoice tray/post

    it notes

    4 Stock

    Quantity

    Integer 1-10 2000 The Quantity of the

    clients order

    N/A Post it Note or Not

    stored

    6 Supplier

    Name

    Text 1-50 Confectionary

    Company

    The name Suppilers

    compnay

    N/A Invoice Tray

    7 Supplier

    Address

    Text 1-250 19 Person Road,

    Milkstreet, West

    Yorkshire

    The address and

    location of the business

    N/A Invoice Tray

    9 Contact

    Number

    String 11-19 01977552671 The Phone Number for

    contacting the supplier

    N/A Invoice Tray

    10 Assorted

    Information

    String 0-1000 Account No

    8384848484r8

    Any extra details such

    as, fax, email etc..

    N/A Post it note

  • 7/31/2019 Computing Final)

    13/127

    Computing Project Page 13

    Interview

    I intend to interview the client for his requirements and the end user of the software (his employees

    that will be using this system on a daily basis).

    Interview Plan

    These are the questions Intend to ask the client:

    - Current Problems facing the companies stock management- Current Technological systems- Whether they need a electronic solution- What needs to be stored-

    Users access to database- How will information be amended in DB- What type of data he wants calculating for the information to be useful- Security- The current dataflow that was identified in the analysis- Prompt on sticky notes and temporary storage of other sensitive data

    Questions and responses:

    - Current Problems facing the companies stock management?We have inaccurate counts of stock information, its often stored onto paper

    that is lost. Its inefficient because manual stock counts are required every

    time a customer makes an enquiry/order. We have had problems locating

    suppliers details and remembering who supplied us with what products

    (especially slow selling products). We dont know the last time contacted

    the suppliers. Often we have problems finding the price for the products

    individually because it requires us to have to search invoices for batches of

    the product.

    - Do you wish to have a electronic Solution to fix the problem facing yourcompany?

    Yes, thats exactly what we need.

    - Current Technological systems running at your work place? Such as Hardwareand Operating Systems?

    We run 5 PCs with Windows XP.

    Follow Up Question: Are They all Networked together?

    No (All Standalone)

    Follow Up Question: How many are used in the Stock ManagementDepartment?

  • 7/31/2019 Computing Final)

    14/127

    Page 14

    Just one machine.

    - What needs to be stored?Item Names is estsinal, so it a brief description incase the customer asks

    about the product, the Stock Quantity and the suppliers details.

    Follow Up: What about Supplier Details? Address etc?Supplier Name, Supplier Address and Contact Number

    Follow Up: You mentioned problems with the last time you contacted the

    supplier, How about the system records that?

    That would be very helpful.

    Follow Up: You mentioned a price problem, how about you record the price

    for the products in the system too?

    That would be perfect

    Follow up: Do you have assorted information such as Account Details and

    vouchers for suppliers?Yes we do. It would be helpful to be able to record that information, in

    relation to the supplier as well.

    - How many Users will access the database?Just a few select people that always use the system. I would prefer to not

    have to train all the users.

    - How will information be amended in system?I would like an initiative interface that would simple to use and not to

    cluttered with the supplier and stock details separated.

    What type of data he wants calculating for the information to be useful?

    I would really like to work out which are the products that we have the

    most stock of, sorting them by stock level would be great. Many a most

    popular stock list would be great, so we could co-ordinate sales efforts.

    - What Security do you want in the system?A Simple Single password would be effective, we just want to stop

    unauthorized people from using the system. All the staff would know the

    password anyway.

    Initial Interview Results

    I interviewed the client and compiled list of responses. I discussed the stock systems

    idea and the problems facing the company currently. I have underlined key

    points/problems that were not initially visible to my client. I established that my client

    would like a electronic system that would be run on a single standalone Computer

    running Microsoft Windows XP. I understand that the client has problems keeping

    account of stock items, the quantity of stock, purchase prices of the items and suppliers

    information (Names, Items they supply, Contact Details, Last Time Contacted and

    assorted information). It is clear that my system will have to solve these problems and

    have some form of database storage to collate the data. He also have expressed an

    interest in reports for the system for things such as most popular items, which would be

  • 7/31/2019 Computing Final)

    15/127

    Page 15

    calculated in system. I will enquiry as to what information would be the most useful to

    my end user by conducting my questionnaire.

    The client understood the problem that faced him and I also got the understanding of

    what the problem was through observation and explanation. He was interested in

    making sure his system was secure with user access to only the information that isnecessary and making sure that only staff can have access to the system. He also

    established he wanted some data saving and turning into useful information in some

    form such as reports. I wish to follow this up with a few more questions but so far I have

    established, my system needs to solve:

    - Keeping account of stock items, the quantity of stock, purchase prices of theitems and suppliers information (Names, Items they supply, Contact Details, Last

    Time Contacted and assorted information).

    - Calculating of reports such as popular items- Security with a password to protect against intrusion- They have windows XP as my distribution platform

    As an initial concept, I have created two theoretical Data stores to store the

    records. This is just to gather what attributes the client wants permanently

    storing.

    Stock Store:

    - Item Name- Item Description- Stock Level- Purchase Price

    Supplier Store:- Supplier Name- Supplier Address- Supplier Contact Number- Supplier Assorted Information- Last Time Contacting the Supplier

    A link to make sure it shows which suppliers supply the items.

    Follow Up Interview

    These are the questions Intend to ask the client:- Record Attributes for Stock and Supplier Store- Output (Email,PDF,Query,Reports,Excel, Print, etc)- Users that will access the system- Rights permission/user access levels

    Questions & Responses:

    - What Record Attributes for Stock and Supplier Store would you like storing.(shown above diagram)?

    All of those will be fine.

  • 7/31/2019 Computing Final)

    16/127

    Page 16

    - What kind of Output would you like? (Email,PDF,Query,Reports,Excel, Print,etc)

    Im not to sure what would be helpful to my staff and what would allow us

    to make the most of your solution.

    - What Users that will access the system?As I stated before, Just a few members of staff that will be trained in the

    system.

    - Would you like Rights permission/user access levels?No that would over complicate your system and cause managing issues for

    people who would be in charge of the system

    Interview Results

    After this second Interview we confirmed some details and also expanded upon other

    features that will be integrated into the potential solution. Giving more information to

    conceptualise and research on. The client also decided upon what record attributes he

    wanted storing. We also established that the client wanted reports formats but didnt

    know specific ones, so Im going to quiz (with the clients approval) my user group. To

    find what formats would be useful for daily use of my solution. Next I established that

    my client didnt want a complicated system with different passwords or user access

    levels, just a simple single log on.

    End User Survey

    Select End User(s):

    My end users are the staff at the company who needs to check the stock level of the products they

    sell. They will check the product amount and the suppliers to see if they can contact them for more

    stock. There are many requirements that the users may want so I conducted a focus group with a

    select range of staff at the company.

  • 7/31/2019 Computing Final)

    17/127

    Page 17

    DFDs

    Analyses of investigation

    Add

    Edit

    Search

    Append

    System Requirements

    Discuss with End Users.

    Options and justifications

    Office 2007. Can Be run, ETC. Has to run on 7. XP not industry standard.

    Clear System Objectives, Shouldnt be able to exit a form with out dialog box. No redundant data,

    update relevant data, restricted user access.

    Initial Research

    I researched into stock management systems that exist on the current market with in a reasonable

    budget and that would meet most of my clients requirements. After an extensive search I found that

    a solution could be made to fit myclients requirements, Microsoft Access could be tailored to my

    client however, it is a little lacking and adds to much functionality. It wouldnt also allow the client to

    have a nice efficient interface with the stock system.

    After a little more research, I came to the conclusion that most generic stock systems are built for

    generic products and with a client that has a standardised stock level policy, however it was clear

    that this might not be the case for my client. So I called him up to confirm a few details and to

    discuss whether or not his system is prone to human error. I asked him whether or not humans that

    are double checked for errors record the manual stock counts. He said that they count manually on

    delivery and dont double check results. Meaning any solution will be accurate only up to the error of

    human counting.

    After more research I have decided that Microsoft Access would be an ideal backend solution for my

    client with the correct functionality for my solution and I decide to use Microsoft Visual Basic.Net for

    my front end development, as I can develop custom functionalityand restrict unnecessary features

    from the user, allowing my solution to be initiative and simple to understand.

  • 7/31/2019 Computing Final)

    18/127

    Page 18

    Currently the system requires a manual stock check of each item as the customer requests it. It also

    requires a count when being delivered. Meaning there are duplicate tasks being done by staff

    members daily and it is inefficient. This poses a number of problems:

    - Manual Counting is Time Consuming- Error can easily occur when manually counting and having no way of checking

    besides counting twice

    - It is slow for the customer to receive the details of stock meaning that theclient can lose custom

    - The information cant be kept track of for certain reports or pricing. Etc

    Potential Solutions

    My solution

    Advantages:

    - Cheap- Built to the clients exact requirements- Works on relevant hardware- Fast development

    Bespoke solution

    Advantages:

    - Built to clients requirements- Will fix the specific purpose- Be efficient

    Disadvantages:

    - Expensive- Time consuming production

    Current system

    Advantages:

    - User already known how to use/do process- Requires no new training or system- Costs nothing to implement

  • 7/31/2019 Computing Final)

    19/127

    Page 19

    Disadvantages:

    - Inefficient- Causes inconsistencies in stock levels- User Error possible

    Generic Solution (Microsoft Access)

    Advantages:

    - Fixes the clients problem- Is cheaper than bespoke- Works with a wide range of hardware

    Disadvantages:

    -

    Has generic features, may not solve all problems in the clients way- May offer to many features- May be slow due to amount features- No build for specific hardware

    End Requirement SpecificationBased on the results collected above and the interview. The requirements the client wants and has agreed to

    are:

    Functional:

    - Reports- Single logon- Fast Stock Search- Adding of Stock Items- Editing of Stock Items- Deletion of Stock Items- Stock & Suppliers Data Stores- Data Sortable in columns- Adding Suppliers- Editing Suppliers-

    Deletions of Suppliers- Relationship between Suppliers and Stock Items- Must work on current hardware- Developed for Microsoft Windows XP and Above- Run on the .Net Framework 3.5 and above- Real time Updating

    User:

    - Simple Interface- Intuitive- Not cost anything

  • 7/31/2019 Computing Final)

    20/127

    Page 20

    - Selectable columns to order data in ascending and descending- Start up form as a menu.

    The location distance between the client and myself poses several problem meaning that I have to

    email all the stages of my work and get confirmation from the client. Below is evidence that the

    client has agreed to the initial requirements and problem definition.

  • 7/31/2019 Computing Final)

    21/127

    Page 21

    Requirement SpecificationThe Final System Requirements and justification for each:

    Functional:

    - ReportsThe client requested other data formats for manipulation of data and to extend the possibilities of the

    system.

    - Single logonThe showed a desire to have single log on system that allows the user to use just one password that

    would between the staff members using the system . The system would only be in use by one person

    at a time.

    - Fast Stock SearchThe request from the client was to have a fast system that allows for the user to search their data

    stores extensively and at speed to increase the effectiveness of the system and to combat the current

    systems problem of speed.

    - Adding of Stock ItemsThe client has an expanding inventory of items, which is why they need the ability to add more items

    into the system. The client also has requested this feature during investigation.

    - Editing of Stock ItemsItems could change price, color, etc. and the client requires the ability to change the attributes of

    items.

    - Deletion of Stock ItemsItem could be no longer stocked or sold by the company meaning that having redundant data would

    slow the system and take up space. The client has requested this during investigation.- Stock & Suppliers Data Stores

    The need for Stock and Supplier data stores to record the information for the system.

    - Data Sortable in columnsThis allows the client to order data in ascending and descending orders for things such as price and

    names allowing. Meeting the search requirements, of the client as outlined in my investigation.

    - Adding SuppliersThe client could find new suppliers or need to add a new supplier for new items which they need the

    ability to add suppliers to the system.

    - Editing SuppliersThe client could need to amend details for suppliers such as address/contact details and other

    attributes to keep the system up-to-date and relevant.

    - Deletions of SuppliersSuppliers could of become irrelevant to the system (e.g no longer trading) and need removing or new

    suppliers could be found for items and require deleting.

    - Relationship between Suppliers and Stock ItemsA relationship between suppliers and stock items need to be made so that the client can identify the

    suppliers with in the system and find the details easily. This was clear from my investigation.

    - Must work on current hardwareThe client wants a solution that doesnt cost any money meaning that I must work with existing

    hardware.

    -

    Developed for Microsoft Windows XP

  • 7/31/2019 Computing Final)

    22/127

    Page 22

    The client doesnt wish to upgrade or change the current operating system, which is Windows XP

    meaning that the system must be usable on that operating system

    - Real time UpdatingThe client would like the system to update in real time so that all information will be correct.

    - Run on the .Net Framework 3.5 and aboveThe clients solution must work on a platform that is supported on Microsoft Windows XP (or Above)and is feasible to be created.

    User:

    - Simple InterfaceThe client requested a simple interface that would be easy to navigate and use for staff.

    - IntuitiveThe client requested a intuitive interface for the staff to use and understand to make the system as

    fast and efficient as possible.- Not cost anything

    The client wishes my total solution to not cost anything which was outlined in my interviews and

    discussions with him.

    - Selectable columns to order data in ascending and descendingThe client wants an interface to order data in columns and tables that order the data in the system in

    a simple way that also meets the functional requirements.

    - Start up form as a menuThe client wishes to have a simple interface that has a menu form on the systems start up.

    I agree to the analysis and system requirements:

    Tommy Hedges (Client): Scott James Bell (Student)

  • 7/31/2019 Computing Final)

    23/127

    Computing Project Page 23

  • 7/31/2019 Computing Final)

    24/127

    Computing Project Page 24

  • 7/31/2019 Computing Final)

    25/127

    Computing Project Page 25

    DesignSystem Objectives

    The Objectives are similar to the requirements specified in my analysis, however I must also consider the

    logical flow of data and processing. I must also make the interface and integrate all the features in a useful

    and intuitive way. In this section instead of large paragraphs and inlogically written sentences, I would

    prefer to bullet point and state the information in a simple way.

    It is my ambition to say in ten sentences what others say in a whole book- Friedrich Nietzsche

    The New System will have to achieve the following objectives:

    General:

    - To create reports that export information about Items and Suppliers into reasonableformats.

    - To have Single logon security that enables a single password to be used to access thesystem

    - Fast Stock Search to find items and suppliers quicklyStock & Suppliers Data Stores that store the following attributes efficiently:

    Stock Store:

    - Item Name- Item Description- Stock Level- Purchase Price

    Supplier Store:

    - Supplier Name- Supplier Address- Supplier Contact Number- Supplier Assorted Information- Last Time Contacting the Supplier

    - The Data would be sorted in columns on the users request- Selected columns would order data in ascending and descending order according to

    the requirements (0-9, A-Z, 9-0, Z-A)

    - Simple Interface for user to navigate and understand- To make the system Intuitive and easily used.- A menu that is loaded upon start up of the system allowing access to the other forms

    on the system

    - A data relationship between the Supplier and Stock Data Store allowing the system tolink them and display the information.

    - Must work on current hardware- Developed for Microsoft Windows

  • 7/31/2019 Computing Final)

    26/127

    Page 26

    - Updating of Fields and Form in Real time- Developed and Executable on .Net Framework 3.5

    Supplier:

    - Adding Suppliers to the system- Editing Suppliers on the system- Deletions of Suppliers on the system

    Stock:

    - Adding of Stock Items to the system- Editing of Stock Items on the system- Deletion of Stock Items on the system

    I agree to the design objective of the system:

    Tommy Hedges (Client): Scott James Bell (Student):

  • 7/31/2019 Computing Final)

    27/127

    Page 27

    Input, Output, Reports and Other Design Elements

    I shall now design the data Inputs, outputs and other elements that will be required with in the

    system and then get the client to agree to the design.

    Data Inputs

    - New Stock Items- New Stock Item Attributes- New Supplier Records Attributes- New Supplier Records

    Data Outputs

    - The Current Stock Item Selected- Search and Results- The reports that are generated in many formats- Stock Levels- Supplier Information

    Processes

    - Amending of the record automatically when stock is removed and when supplier lastsupplied

    - Security Locking of Forms- Updated Stock Record- Sorting Information into a logical order when requested-

    Searching through fields

    - Processing and formatting the reports correctly

  • 7/31/2019 Computing Final)

    28/127

    Computing Project Page 28

    Data Flow Diagrams of system

    Context Diagram

    Problems:

    - No date for replenished stock levels

    to customer.

    Customer Order Check Stock

    Supply OrderOrder

    Store

    Item

    Insufficient Stock Information

    Suppliers

    Stock

    Order

    1 Stock file

    2 Su l ier file

    D0Stock Store

    - Item

    - Description

    - Stock level

    - LAST Suppl ier ID

    D1 Supplier Store- Supplier Name- Suppl ier Address

    - Last Time Contacting Supplier

    - Assorted Information

    - Supplier ID

  • 7/31/2019 Computing Final)

    29/127

    Page 29

    Draft: Data Flow Diagram (Level 0)

    Stock In

    Order Out

    Stock Level Count

    Stock Request0 D0 Stock Store

    Find supplier

    1

    Contact Supplier

    2

    Order Stock

    3

    D1 Supplie

    r Store

    Receive and order

    delivery note

    6

    D3 Delivery note

    Process Order

    4

    D3 Supplier Store

    Amend Stock

    5

    Delivery Note

  • 7/31/2019 Computing Final)

    30/127

    Page 30

    After some considerations I have decide that is design is to complex and out of the systems scope. It has the necessary processes however lacks some

    context and wouldnt be appropriately designed to slow the logical flow of my system.

    Data Flow Diagrams Level 0:

    Customer 1

    Process Order

    3

    Supply Order

    Order

    Store

    Item

    Insufficient Stock Information

    Suppliers

    Stock

    Order

    1 Stock file

    2 Su lier f ile

    2

    Check Stock

    Level

    0

  • 7/31/2019 Computing Final)

    31/127

    Page 31

    Data Flow Diagram Level 1

    2 Check Stock Level

    2.1

    Organise Clients

    Requirements

    2.2

    Search Stock File

    2.3

    Return Stock Level On

    Items

  • 7/31/2019 Computing Final)

    32/127

    Computing Project Page 32

    Designs for Input Screens, Output Screens and Reports

    Menu

    - Have buttons that load other forms in the system.- Lock button that loads the locking algorithm.

    Stock Item Input

    - Connection to Stock Item Data Store- Item Attributes stored in Text Boxs- Labels explaining each Text boxs function- Saving Button adding the data to the database- Close Button to close the form without adding the item to the database- Validation with Message Boxes to show incorrect inputs

    Stock Item Searching

    - Connection to Stock Item Data Store- Data Grid to display the Item Attributes orderable by Columns and selectable rows

    for exporting.

    - Save and Close button to edit the data in database and close the form.- Export entire table button allowing the data grid to be exported to the export form- Search Field that searchs upon keystroke Enter and returns the results to the data

    grid

    - Export Selected Item in the tablesSupplier Item Input

    - Connection to the Supplier Data Store- Supplier Attributes Stored In Text Boxs- Labels Explaining each Text Boxs Function- Saving Button adding the data to the database- Close Button to close the form without adding the item to the database- Validation with Message Boxes to show incorrect inputs

    Suppliers Search

    - Connection to the Supplier Data Store- Data Grid to display the Item Attributes orderable by Columns and selectable rows

    for exporting.

    - Save and Close button to edit the data in database and close the form.

  • 7/31/2019 Computing Final)

    33/127

    Page 33

    - Export entire table button allowing the data grid to be exported to the export form- Search Field that searchs upon keystroke Enter and returns the results to the data

    grid

    - Export Selected Item in the tables-

    Exporting

    - Accepting of parameters from other forms- Connection to the Supplier and Stock Store- Checkboxs to select which Attributes to be exported- The ability to select the format of the exported file- Close Button to end the connections and dump any parameters-

    Export button with a dialogue to save the file

    Password Management

    - Load password from file- Compares current password to user input- Changes Password- Saves New Password

  • 7/31/2019 Computing Final)

    34/127

    Page 34

    I agree to and have reviewed the Input, Output, Processes and Forms requirements:

    Tommy Hedges (Client): Scott James Bell (Student):

  • 7/31/2019 Computing Final)

    35/127

    Page 35

    Potential problems replacing the old system

    There could be potential problems that could cripple any solutions deployment/the companies daily

    operations.

    However, for my client I have decided on a full replacement of the system being the most efficient

    and useful. My client would perform a full stock check on the day of installation of my solution,

    which would, then have all the data input. Creating a fully functioning deployed system that is

    installed and working within one business day causing no real economic effect to company.

    Staff training could cause problems for the system but we have decided on training them on test

    systems before deployment meaning that they would not only help identify any operating bugs

    missed while extensive testing had taken place but also understand and use the system. User

    Instructions shall also be given with the finished system for new staff members and troubleshooting.

    Software/Hardware

    Requirements

    Justification

    Windows XP Operating System used by company and used

    to run VB.NET

    Visual Basic.NET Software selected to create and run the

    system

    Desktop PC A desktop pc that is already used by staff will

    be integrated into the solution to meet my

    clients requirement of not purchasing any

    item to make a solution.

    Microsoft Excel Used to open Exported files by my solution

  • 7/31/2019 Computing Final)

    36/127

    Computing Project Page 36

    -File and Data Structure

    Record

    no

    Record

    Name

    Data Type Range Example Data Description Validation Data Store

    1 Item ID Integer

    (auto

    Generated)

    1-200 1 An auto generated

    Number to keep the

    product located and

    have an unique

    Identification with in the

    system.

    Auto generated.

    Not editable

    Stock Store

    2 Item Name String 1-25

    Char

    Marshmallows The Products name. N/A Stock Store

    3 Purchase

    Price

    Single 1-5 12.79 The price of the Product

    as its currently being

    sold

    Only numbers to 2

    Decimal Points

    Stock Store

    4 Stock

    Quantity

    Integer 1-10 2000 The Quantity of the

    clients order

    Stock Store

    5 Description String 0-500

    A spongy

    confection madefrom a soft

    mixture of sugar,

    albumen, andgelatin.

    Description of the

    product and similar

    products!

    N/A Stock Store

    6 Supplier

    Name

    String 1-50 Confectionary

    Company

    The name Suppilers

    compnay

    Check for

    Duplicates

    Supplier Store

    7 Supplier

    Address

    String 1-250 19 Person Road,

    Milkstreet, West

    Yorkshire

    The address and

    location of the business

    N/A Supplier Store

  • 7/31/2019 Computing Final)

    37/127

    Page 37

    8 Last Time

    Contacting

    Supplier

    DateTime 8 08/09/1998 The last date that the

    company contacted the

    supplier

    Date Thats Current Date

    Non Numerical Value Entered Into Contact

    Number Field

    A Value that is invalid has been entered into the

    Contact number Field

    I have reviewed the system and tested it against my requirements with comments as above of the

    proposed system:

    Tommy Hedges (Client): Scott James Bell (Student)

  • 7/31/2019 Computing Final)

    77/127

    Computing Project Page 77

  • 7/31/2019 Computing Final)

    78/127

    Page 78

    Evidence of modification

  • 7/31/2019 Computing Final)

    79/127

    Computing Project Page 79

    User DocumentationWelcome to the Installation, User and Maintenance Manual for Anchor

    Supplies Stock System. Below you will find all the information in various

    subheadings in order to make the most of your Stock Management

    Solution. A copy of this instructional guide in a PDF (Portable Document

    Format) is included with your installation folder.

    USER DOCUMENTATION ...............................................................ERROR! BOOKMARK NOT DEFINED.

    SYSTEM REQUIREMENTS ................................................................................ERROR!BOOKMARK NOT DEFINED.

    INSTALLATION &START UP...........................................................................ERROR!BOOKMARK NOT DEFINED.

    INSTALLATION................................................................................................. ERROR!BOOKMARK NOT DEFINED.START UP......................................................................................................... ERROR!BOOKMARK NOT DEFINED.

    TYPICAL USE.................................................................................................... ERROR!BOOKMARK NOT DEFINED.

    MENU ....................................................................................................................... ERROR!BOOKMARK NOT DEFINED.

    ADD ITEM ................................................................................................................ ERROR!BOOKMARK NOT DEFINED.

    ADDING SUPPLIER .................................................................................................. ERROR!BOOKMARK NOT DEFINED.

    STOCK SEARCH........................................................................................................ ERROR!BOOKMARK NOT DEFINED.

    SUPPLIER SEARCH .................................................................................................. ERROR!BOOKMARK NOT DEFINED.

    BACK UP ........................................................................................................... ERROR!BOOKMARK NOT DEFINED.

    TROUBLESHOOTING........................................................................................ ERROR!BOOKMARK NOT DEFINED.

    GLOSSARY........................................................................................................ ERROR!BOOKMARK NOT DEFINED.SUPPORT.......................................................................................................... ERROR!BOOKMARK NOT DEFINED.

    System Requirements

    The End User must be running a Windows based Operating system that supports Microsoft .Net 3.5

    anything from Microsoft Windows XP and Above (Including Microsoft Windows Vista & 7). The

    computer must have a minimum of 256MB of memory and must have 120 MBs of Free Memory.

    Peripherals Required: Mouse, Keyboard & Monitor.

    Minimum Requirements:

    - Microsoft Windows XP (SP3) & Above- Microsoft .NET Framework 3.5 & Above- 256MBs ofRandom Access Memory- 120 MBs of Free Hard Disk Space- Mouse- Keyboard- Monitor

  • 7/31/2019 Computing Final)

    80/127

    Page 80

    Important Note: Microsoft Windows XP Operating system is due to expire the support period so our

    product cant be guaranteed to work at the end of 2012. We would recommend upgrading to a later

    version of the Windows Operating System.

    Installation & Start Up

    Installation

    Installation is a simple and easy for the Anchor Supplies Stock System, all that is required is for you

    to open up the Executable File Called Anchor Supplies Installer included with the Document. It will

    then take you through an installation wizard as seen below.

    Installation Loading Screen:

    Installation Welcome Message:Just click next to continue

    Installation Directory: Change the Directory to suit your installation needs and Click Next to continue.

    (Note Remember the directory as it will be useful later on in this guide)

  • 7/31/2019 Computing Final)

    81/127

    Page 81

    Installation information Overview:A final Overview of your installation, confirm this is correct and

    click next.

    Installation Screen: This is while the product is installing, it may take a few moments to install.

    Installation complete: Your new Stock System is ready to be

    used.

    Your Application is now Available in the start menu and on the Desktop. Click the Short cut to

    execute the program.

  • 7/31/2019 Computing Final)

    82/127

    Page 82

    Start Up

    To start the application simply follow the instructions below:

    Step 1: Navigate to the Desktop of your Computer. A new Shortcut will appear on your desktop, this

    is the Anchor Supplies Stock System.

    Method 2:

    Step 1: Navigate and open the Start Menu

    Step 2: Double click

    this icon and the

    application will

    start.

  • 7/31/2019 Computing Final)

    83/127

    Page 83

    Step 2: Browse to

    All Programs then

    Anchor Supplies

    Stock System and

    Double Click theShortcut to the

    executable file to

    start the

    application

    A copy of this

    instructional guide

    is also included in

    this folder

  • 7/31/2019 Computing Final)

    84/127

    Page 84

    Typical Use

    Menu

    This is the User Menu which allows you to access the various systems the stock system and is loaded

    upon start up of the application. This menu will always be open but in the background of application

    allowing you to close one form and open another seamlessly. Below is an explanation of each

    feature and button on the menu form.

    The Add Item

    Button loads the

    Add Item Form

    The Add Supplier

    Button loads the

    Add Su lier Form

    The Stock Search

    Button loads the

    Stock Search Form

    The Supplier

    Search Button

    loads the Supplier

    Search Form

    The Export Button

    loads the Export

    Form

    The Lock Button Locks the

    buttons and closes any

    open forms. (fig

    2)Requiring a password to

    be entered before allowing

    user (fig 3) interaction

    again

    Figure 2

    All the Buttons

    become locked when

    the form is in locked

    mode and any open

    forms are closed

    The Change Password Button

    loads an Input dialog for the

    user to update their

    password

    The Unlock button load

    the Enter password

    dialog (fig 3) for the user

    to unlock the form

  • 7/31/2019 Computing Final)

    85/127

    Page 85

    Below is the Enter password Input Dialog for the user to resume their work with the system.

    They must enter the password correct to have access back to the system. There is no lockout times r

    functions so the user may make as many attempts as they wish.

    Figure 3

    This shows the password failure

    message box.

  • 7/31/2019 Computing Final)

    86/127

    Page 86

    Add Item

    This is the user information for adding items to the system using the Add Item Form. Below is a

    detailed account of what each button does on the forms and a step by step guide on how to use this

    dialog.

    Adding an Item

    You must follow the instructions (Top to Bottom) in order to add a new item.

    Auto GeneratedNumber

    Items Name Field with a

    maximum length of 25

    Characters

    Items Description Field with a

    maximum length of 500

    Characters

    Items Price Field

    Requirements: 2 decimalplaces, Numeric and a positive

    integer.

    Items Supplier ID Combo Box

    with a list of su lier Names

    Record Controls ADD

    Save

    Click Add New Item

    ButtonEnter the new Items Name

    with a maximum length of 25

    Characters

    Enter the new Items

    Description with a maximum

    length of 500 Characters

    Enter the new Items Price to 2

    decimal places and that is a

    positive integer. It also must

    be numeric

    Select the New Items Supplier

    ID from the dro down list.

    Click Save Button

  • 7/31/2019 Computing Final)

    87/127

    Page 87

    Adding Supplier

    This is the user information for adding Suppliers to the system using the Add Supplier Form. Below is

    a detailed account of what each button does on the forms and a step by step guide on how to use

    this dialog.

    Auto Generated

    Number

    Record Controls ADD

    Supplier Name Field with a

    maximum length of 25

    Characters

    Supplier Address Field with a

    maximum length of 500

    Characters

    Last Time Contacting Supplier

    Date Time Picker, Allows you

    to select a date before the

    current systems Date.

    Assorted Information Field

    with a Maximum of 500

    Characters

    Save

    Adding a Supplier

    You must follow the Instructions (Top to Bottom) in order to a new supplier

    Click Add New Item

    Button

    Enter the new Suppliers Name

    with a maximum length of 25

    Characters

    Enter the new Suppliers

    Address with a maximum

    length of 500 Characters

    Select a Date on the Last Time

    Contacting Supplier Date Time

    Picker, select a date before

    the current systems Date.

    Add Information to theAssorted Information Field

    with a Maximum of 500

    Characters

  • 7/31/2019 Computing Final)

    88/127

    Page 88

    Stock Search

    This is the user information for Searching Stock on the system using the Stock Search Form. Below is

    a detailed account of what each button does on the forms and a guide on how to use this form.

    rrent row

    lected,

    eful for

    porting

    ngle items

    d

    vigating

    These are the column headers

    allowing you to order the data in any

    way you wish.

    Single row of

    data containing

    the items

    attributes and

    can beedited/deleted

  • 7/31/2019 Computing Final)

    89/127

    Page 89

    Supplier Search

    This is the user information for Searching Suppliers on the system using the Supplier Search Form.

    Below is a detailed account of what each button does on the forms and a guide on how to use this

    form.

    Single row ofdata containin

    the suppliers

    attributes and

    can be

    edited/deleted

    These are the column headers

    allowing you to order the data in any

    way you wish.

    rrent

    w

    ected,

    eful for

    porting

    gle

    ms and

    vigating

  • 7/31/2019 Computing Final)

    90/127

    Page 90

    Exporting

    This is the Exporting Form which allows you to Export to a range of formats for your leisure. You

    many export to either Microsoft Excel & Text format. Below is an explanation of each feature and

    button on the menu form.

    This is the Attribute Checkboxs

    with the selections for

    exporting. With the required

    attributes for any export

    preselected.

    The Export Option

    Combination Box Allows the

    user to select the format they

    wish to export.

    The export button shows a file

    dialog (fig 4) to save the file in

    the users desired directory.

    Exporting

    You must follow the Instructions (Top to Bottom) in order to a new supplier

    Select the desired Attributes

    you wish to be exported.

    Select which format you wish

    to export too.Select the Export button when

    everything is right and a file

    dialog shall load (fig 4).

  • 7/31/2019 Computing Final)

    91/127

    Page 91

    Figure 4

  • 7/31/2019 Computing Final)

    92/127

    Page 92

    Back up

    Backing up your system is an essential part of operation; any data loss could be potential threating

    to your daily business routine. So we have made several options to back up your system: that

    involve manual work as well as automated solutions for ease of use. We would recommend you back

    up your system on a regular basis in order to protect against failures to your system and protect any

    valuable data.

    Solution One: Exporting To Excel

    As Shown in the above instructions, you can simply just export your entire database to Microsoft

    Office Excel and easily access it in the application should you wish for your data to be backed up.

    Solution Two: Exporting to Text Documents

    As Shown in the above instructions, you can simply just export your entire database to a plain textfile and easily access it should you wish for your data to be backed up.

    Solution Three: Copying your database

    Copying the Database

    The best and full proof method of backing up is to back up your database file which will allow you to

    restore your system should a problem arise. You can simply reinstall the software and replace the

    blank database with your pre-existing one. Below is a step by step guide on how to back up your

    database file.

    Step 1: Browse to the location of the

    installed system usually

    C:/Windows/Program Files/Anchor

    Supplies Stock System (As Below) but

    you may of change this during

    installation.

  • 7/31/2019 Computing Final)

    93/127

    Page 93

    Step 2: Open up that directory and select the

    anchor supplies.accdb file (This is your

    database Be careful not to move it) and

    select copy from the right click option menu.

    Step 3: Paste the Database file to the backup directory (Choose your own). We would recommend a

    location that is not on the computer for maximum safety.

  • 7/31/2019 Computing Final)

    94/127

    Page 94

    Disclaimers: Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT

    PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHTHOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM AS IS WITHOUT WARRANTY OF ANY

    KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES

    OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE

    QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE

    DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

    Troubleshooting

    Error Reason for error Solution

    Invalid PasswordYour password is incorrect and

    doesnt match the password stored in

    the system

    Either enter the correct

    password or Browse to

    C:/Windows/Program

    Files/Anchor Supplies Stock

    System/ and create a

    document called password.txt

    with your new desired

    password.

    Error Connecting to the

    database

    Your database isnt in the required

    location for the application to load it.

    Copy/move your database to

    your installation location.Typically,

    C:/Windows/Program

    Files/Anchor Supplies Stock

    System or the directory where

    your applications executable

    file is located.

    Runtime Error Either your Operating Systems .Net

    Framework is damaged or The

    applications Executable file isdamaged.

    Initially reinstall .Net

    Framework (Minimum Verison

    3.5). If this doesnt fix the errorthen reinstall the application

    following the instructions

    below. However, make sure

    you back up your database and

    replace the default database

    after installation.

  • 7/31/2019 Computing Final)

    95/127

    Page 95

    Glossary

    Microsoft Windows XP:an operating system produced by Microsoft for use on personalcomputers, including home and business desktops, laptops, and media centers. It was first

    released in August 2001, and is currently one of the most popular versions of Windows. The

    name "XP" is short for "eXPerience." [Wikipedia Source -

    http://en.wikipedia.org/wiki/Microsoft_XP]

    Microsoft Windows Vista: an operating system released in several variations developed by

    Microsoft for use on personal computers, including home and business desktops, laptops, tablet PCs,

    and media center PCs. [Wikipedia Source -http://en.wikipedia.org/wiki/Microsoft_Vista]

    Microsoft Windows 7:the current release of Microsoft Windows, a series of operating systemsproduced by Microsoft for use on personal computers, including home and business desktops,

    laptops, netbooks, tablet PCs, and media center PCs. [ Wikipedia

    Source -http://en.wikipedia.org/wiki/Microsoft_7]

    Microsoft .NET Framework:The Microsoft .NET Framework is a software framework that can beinstalled on computers running Microsoft Windows operating systems. [ Wikipedia Source -

    http://en.wikipedia.org/wiki/Microsoft_net_framework]

    Microsoft Excel:is a commercial spreadsheet application written and distributed by Microsoftfor Microsoft Windows. [Wikipedia - Source - http://en.wikipedia.org/wiki/Microsoft_Excel ]

    Random Access Memory: the most common computer memory which can be used by programs to

    perform necessary tasks while the computer is on; an integrated circuit memory chip allowsinformation to be stored or accessed in any order and all storage locations are equally accessible.

    [Princeton University Source - http://wordnetweb.princeton.edu/perl/webwn?s=ram]

    Hard Disk: A storage medium for data inside your computer.

    MB: Megabyte is a unit of information that is used in a computer system. It is a size of memory

    equating to (1024KB)

    Runtime Error: A run-time error is detected after or during the execution of a program [ Wikipedia

    Source - http://en.wikipedia.org/wiki/Run_time_(program_lifecycle_phase) ]

    Database: is an organized collection of data, today typically in digital form. The data are typically

    organized to model relevant aspects of reality (for example, the availability of rooms in hotels), in a

    way that supports processes requiring this information (for example, finding a hotel with vacancies).

    [Wikipedia Source - http://en.wikipedia.org/wiki/Database]

    Support

    If any issue arises with the system and you require additional help contact support on

    [email protected]

    Thank you for co-operation

    mailto:[email protected]:[email protected]:[email protected]
  • 7/31/2019 Computing Final)

    96/127

    Page 96

  • 7/31/2019 Computing Final)

    97/127

    Page 97

    Evaluation

    Requirement Met? Proof Comments

    To create reports that export information about Items

    and Suppliers into reasonable formats.

    Yes Above Yes as stated above the

    System Exports to

    Microsoft Excel allowing

    for data to be

    manipulated

    A data relationship between the Supplier and Stock

    Data Store allowing the system to link them and display

    the information.

    To have Single logon security that enables a single

    password to be used to access the system

    Yes Above Yes the software is

    secured with an input

    box and this meets the

    criteria of the client

    Fast Stock Search to find items and suppliers quickly Yes Above The user can search as

    well as organise and edit

    the searchs fast.

    Stock & Suppliers Data Stores that store the

    following attributes efficiently:

    Stock Store:

    - Item Name- Item Description- Stock Level- Purchase Price

    Supplier Store:

    - Supplier Name- Supplier Address- Supplier Contact Number- Supplier Assorted Information- Last Time Contacting the Supplier

    Yes Above From day one of

    development I have

    included the agreed

    upon attribute with

    appropriate file sizes.

    The Data would be sorted in columns on the users

    request

    Yes Above The User can select any

    column or row in the

    Searching Forms for

    both Supplier and Item.

  • 7/31/2019 Computing Final)

    98/127

    Page 98

    Selected columns would order data in ascending and

    descending order according to the requirements (0-9,

    A-Z, 9-0, Z-A)

    Yes Above The data is sorted on

    user interaction with the

    and can identify the

    solution

    Simple Interface for user to navigate and understand Yes Below The clients comments

    agree with this and end

    user survey too

    To make the system Intuitive and easily used. Yes Above After some

    considerations and due

    to the time constrains on

    the project, I decided to

    integrate a simple and

    helpful user guide that isaccessible in paper and

    digital formats for the

    user for them to

    understand the system. I

    believe that the system

    however could be used

    and understood without

    prior knowledge

    A menu that is loaded upon start up of the systemallowing access to the other forms on the system

    Yes Above Yes as can be screen byscreenshot evidence.

    A data relationship between the Supplier and Stock

    Data Store allowing the system to link them and display

    the information.

    Yes Above Yes the entity

    relationship diagram

    shows the relationship

    between the tables with

    a foreign key.

    Must work on current hardware Yes Above Yes works on the current

    machines

    Developed for Microsoft Windows Yes Above It is developed for

    Microsoft Windows XP

    and Above

    Updating of Fields and Form in Real time Yes Above Yes upon interaction

    with the system

    Developed and Executable on .Net Framework 3.5 Yes Above Yes it works on the .net

    framework 3.5 and

  • 7/31/2019 Computing Final)

    99/127

    Page 99

    The solution didnt cost any money and met the requirements as specified above

    Tommy Hedges (Client): Scott James Bell (Student):

    above

    Adding Suppliers to the system Yes Above Easy for the client to add

    new suppliers to the

    system

    Editing Suppliers on the system Yes Above Easy for my Client to edit

    the supplier attributes

    for system.

    Deletions of Suppliers on the system Yes Above Easy and simple for the

    client to delete suppliers

    from the system.

    Adding of Stock Items to the system Yes Above Easy for the client to add

    new stock items to the

    system

    Editing of Stock Items on the system Yes Above Easy for my Client to edit

    the stock attributes for

    system.

    Deletion of Stock Items Yes Above Easy and simple for the

    client to delete stock

    from the system.

  • 7/31/2019 Computing Final)

    100/127

    Page 100

    Problems and Limitations When Creating The System

    The Main Problem after agreeing upon the solution requirements with my client was implementing

    them all with the required time frame and keeping a certain complexity in the system even though

    my clients requirements were quite simple. I soon realised that my approach was to overcomplicate

    the design and development of the solution by thinking to generic and big. I had to prioritisereconvene with my client on regular intervals to make sure I was completing the system in a user

    friendly way. For this I decided not to include the following:

    - A popular products section for stock itemsThis feature was really outside of my designs scope and added to much complexity

    to the system. Because of the way Stock Levels and History would have had to of

    been complied for the this to be calculated.

    - Help Menu on the applicationHelp Menus were a pointless feature to the user because the system is very intuitive

    and an extensive but usable user guide was included with installation.

    If I had the necessary time to complete this project I would of tried to rescope my solution to include

    them. I also encountered problems during the programing of my solution these were:

    - Using a database into this system was a challenge as I had only ever used SQL serverand Visual Basic.Net together and not ever used Microsoft Access database files. I

    now more confident in using Access and VB.Net

    - The Access file only allowed strings to be 255 characters long when I hadrequirements of 500. I found a work around that allowed my system to work andinclude the required components.

    - I had never exported to Microsoft Excel before and it took a long time to write anapplication wrapper, which caused many problems for my program exporting

    functionality. I have since leant the knowledge and even made it so my module could

    be easily adapted to future projects

    - I originally forgot the scope of the password leaving it as a variable only to relies itwould be reinitialized on restart meaning my security would be useless. I wrote a

    text file, which was securely scrambled and allows the password to be stored safely.

    Good and Bad Points Of The System

    Some of the good points of the system are:

    After examining the Initial specification, interviews and definition of the problem I have accurately

    fixed the problem that faced my client and met the system requirements in an efficient manner. One

    of the best things about my system is the export feature, as it gives my client versatility and

    flexibility with data from the system. This not only allows backing up but the data to be manipulated

    in other applications to allow extra user ability and features outside of the scope of my product.

    My system also keeps track of the item level very well with the column reordering, allowing the user

    to manipulate and interpret the data in my system in an effective and useful way. As for using the

  • 7/31/2019 Computing Final)

    101/127

    Page 101

    system its self, my users have found it easier to use and it means that the various staff members

    could take over the system with minimal training as requested by my client.

    Some Bad Points of My system:

    Unfortunately, my system allows for problems with the export feature, such as if the data is neededto be selected individually it is often unreliable to make sure the currently selected row is exported

    meaning the user would possibly have to try several times to make sure the correct information is

    selected.

    Another bad point is that data entered could always be prone to human error as mentioned in my

    analysis meaning that the system could possibly be inaccurate due circumstances out of its control.

    End User Report

    I have asked 5 end users to evaluate the system against the requirement; I have done this by

    creating a scenario:

    Scenario:

    Add a new item (Item Name: Tent, Item Description: A 2x2 tent, Purchase Price: 12, Stock Level: 25,

    Supplier ID 1)

    Was this task easy to-do?

    Yes 5

    No 0

    User Comment(s):

    Easy

    Simple

    Edit the stock item changing the stock level to 12 and the supplier ID to 2

    Was this task easy to-do?

    Yes 5

    No 0

    User Comment(s):

    Easy

    A little bit hard to change the supplier ID, if there wasnt an supplier in the system, lucky there was.

    Delete a stock item

  • 7/31/2019 Computing Final)

    102/127

    Page 102

    Was this task easy to-do?

    Yes 5

    No 0

    User Comment(s):

    Was easy todo

    I tried right clicking first but the buttons make it easy

    Add a supplier (Supplier Name: Test, Supplier Address: Test Street, Contact number: 01977562621,

    Assorted Information: 123344, Last time contacting supplier: 12/02/2012)

    Was this task easy to-do?

    Yes 5

    No 0

    User Comment(s):

    Easy todo

    A error message was shown for an incorrect input in the date.

    Edit a supplier (Last time contacting supplier: 23/02/2012)

    Was this task easy to-do?

    Yes 5

    No 0

    User Comment(s):

    Allowed me to change it easily

    Delete a supplier

    Was this task easy to-do?

    Yes 5

    No 0

    User Comment(s):

    Allowed me to delete the record quickly.

    Sort a column

    Was this task easy to-do?

  • 7/31/2019 Computing Final)

    103/127

    Page 103

    Yes 3

    No 2

    User Comment(s):

    Without proper instruction it was difficult but was easy once I read the documentation.

    Export a table

    Was this task easy to-do?

    Yes 5

    No 0

    User Comment(s):

    Exporting a table was quite easy and quick

    Evaluation of End Users Report

    The users responded well to the system and the feedback was useful to show that the system had

    met the requirements. The system shows that the user can use the system with little to no

    instruction, which means that its intuitive and easy to navigate. The systems validation was simple

    and understood by the user meaning that they could respond to the problems and correctly enter

    the information. The information collected has provided insight into the how the users have

    interacted the system, it is clear that the users struggled slightly with sorting columns which could be

    improved upon by adding a tooltip on mouse over of the columns/table fields with the information

    on how to reorganise columns. This would be possible in extensions of the system (see Possible

    Extensions). Overall my end users seem to have a positive review of the system.

    Possible Extensions

    Adding a popular stock item calculations

    This could be achieved by storing stock history for items and suppliers. It would allow for calculations

    of the most popular products, which was a request by my client but was not able to be completed in

    my systems scope. It would improve the system, as the client would be able to keep track of popular

    products and order more in bulk to be efficient. It would also allow my client more control of stock

    flow, with a consistent flow of popular stock into his warehouse. I would go about adding this, bystoring a stock added level and date added into a separate database with a separate interface

  • 7/31/2019 Computing Final)

    104/127

    Page 104

    allowing the client to select criteria to search the stock level history against the current level with

    reference to how long it took to sell the amount of products recorded. It would check the stock

    added history against the current systems time to provide a accurate timescale for my client.

    Printing

    It would allow my user a direct function to print out data from the system. Instead of requiring the

    document to be sent out to excel before being able to print. It would have been useful for my end

    users and allowed for a better system/interaction. I would implement this using the Visual Basic,

    Printing Library and Dialogue Box functionality to create a simple intuitive layout for the client to use

    which would have to meet my system requirements about navigation and user interactions.

    Automated Back Ups and restores

    It would allow for the client to have a data efficient system that is safe and not prone to manual back

    up error. This would be integrated into the closing down of the application, as the application is

    closed, I would implement Visual Basics System.IO library to save a copy of the current data in the

    database which could be restored upon boot, if an error is to occur with the database/solution. It

    would allow my client to have a reliable and safer solution that could would be more stable.

    Tool Tips for Column Sorting

    In the User Scenario it was evident that some users struggled when trying to reorganise the columns

    with out the user documentation, which means that it would be useful to add some tool tips(

    information dialogue on mouse over of certain elements of applications). I would of liked to

    integrate this to help the user understand the system easier and make the system more intuitive. I

    would do this by adding the tools tips on the columns headers and the fields that can be sorted in

    the tables.

    Conclusion

    I am satisfied with my solution and the documentation above:

    Tommy Hedges (Client): Scott James Bell (Student)

  • 7/31/2019 Computing Final)

    105/127

    Computing Project Page 105

    Appendix

    Menu Form

    Public Class MENU

    Friend WithEvents btnlock As System.Windows.Forms.Button

    Friend WithEvents Button1 As System.Windows.Forms.Button

    Friend WithEvents btn_additem As System.Windows.Forms.Button

    Friend WithEvents Button2 As System.Windows.Forms.Button

    Friend WithEvents Button3 As System.Windows.Forms.Button

    Friend WithEvents Btnlock1 As System.Windows.Forms.Button

    Friend WithEvents Button5 As System.Windows.Forms.Button

    Friend WithEvents Button4 As System.Windows.Forms.Button

    Friend WithEvents GrpMenu As System.Windows.Forms.GroupBox

    Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

    Btnlock1.Hide()

    End Sub

  • 7/31/2019 Computing Final)

    106/127

    Page 106

    Public Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles

    btnlock.Click

    Try

    Dim Passwordtextloader As System.IO.TextReader

    Passwordtextloader = System.IO.File.OpenText("C:/Windows/Program Files/Anchor Supplies Stock

    System/password.text)

    Catch Ex As Exception

    Dim password As String = Passwordtextloader.ReadToEnd

    Passwordtextloader.Close()

    End Try

    'Password in a variable

    Do While InputBox("Enter passwor