-
- 1 1
- 2 2
- 3 3
- 4 4
- 5 5
- 6 6
- 7 7
- 8 8
- 9 9
- 10 10
- 11 11
- 12 12
- 13 13
- 14 14
- 15 15
- 16 16
- 17 17
- 18 18
- 19 19
- 20 20
- 21 21
- 22 22
- 23 23
- 24 24
- 25 25
- 26 26
- 27 27
- 28 28
- 29 29
- 30 30
- 31 31
- 32 32
- 33 33
- 34 34
- 35 35
- 36 36
- 37 37
- 38 38
- 39 39
- 40 40
- 41 41
- 42 42
- 43 43
- 44 44
- 45 45
- 46 46
- 47 47
- 48 48
- 49 49
- 50 50
- 51 51
- 52 52
- 53 53
- 54 54
- 55 55
- 56 56
- 57 57
- 58 58
- 59 59
- 60 60
- 61 61
- 62 62
- 63 63
- 64 64
- 65 65
- 66 66
- 67 67
- 68 68
- 69 69
- 70 70
- 71 71
- 72 72
- 73 73
- 74 74
- 75 75
- 76 76
- 77 77
- 78 78
- 79 79
- 80 80
- 81 81
- 82 82
- 83 83
- 84 84
- 85 85
- 86 86
- 87 87
- 88 88
- 89 89
- 90 90
- 91 91
- 92 92
- 93 93
- 94 94
- 95 95
- 96 96
- 97 97
- 98 98
- 99 99
- 100 100
- 101 101
- 102 102
- 103 103
- 104 104
- 105 105
- 106 106
- 107 107
- 108 108
- 109 109
- 110 110
- 111 111
- 112 112
- 113 113
- 114 114
- 115 115
- 116 116
- 117 117
- 118 118
- 119 119
- 120 120
- 121 121
- 122 122
- 123 123
- 124 124
- 125 125
- 126 126
- 127 127
- 128 128
- 129 129
- 130 130
- 131 131
- 132 132
- 133 133
- 134 134
-
- Level: AS and A Level
- Subject: ICT
- Word count: 16932
Cunha & Ribeiro Ltd: Stock Control & Invoice Database
Extracts from this document...
Introduction
Cunha & Ribeiro Ltd: Stock Control & Invoice Database Centre Name: Parliament Hill School Centre Number: Candidate Name: Carlos Fernandes Candidate Number: Table of Contents Analysis 6 Problem Definition 7 Background to the Company 7 Initial Problem Definition 7 The Current System 8 Data Flow in Current System 10 Origins of Data 10 Analysis of Current System 11 Restatement of Problem 11 Investigation and Analysis 12 Justification of Methods of Fact-Finding 12 Fact Recording: 2 12 Analysis of Data 14 Requirements Specification 14 Agreement from Organisation to Requirements 17 Alternative Approaches 18 Selected Approach 20 Acceptance from Organisation to Selected Approach 21 Hardware Requirements 22 Design 23 Nature of the Solution 24 Set of objectives 24 Design Specification 25 Input 25 Customer Details Input Document: 25 Delivery Appointments Input Document: 26 Sales Details Input Document: 27 Available Stock Input Document: 28 Payment Plan Input Document: 29 Customer Details Input Screen: 30 Sales Details Input Screen: 32 Stock Input Screen: 33 Payment Plan Input Screen: 34 Processing 35 Output 38 Delivery Report: 39 Out-Standing Payments Report: 40 Available Stock Report: 41 Append Query: 41 User Interface 42 Report Switchboard 43 Error Messages 44 Files and Data Structures 44 File Sizing 48 System Diagrams 51 Task Model 53 User Agreement of Design Specification 55 Intended Benefits 56 Benefit 1 56 Benefit 2 56 Benefit 3 56 Limitations of the System 58 Limitations 58 Hardware: 58 Software: 58 User: 58 Imposed: 59 Scalability 59 Software Development Testing and Implementation 60 Development and Testing 61 Annotated Listing 61 Switchboard 61 Available Stock 63 Customer Details 64 Delivery Appointments 65 Payment Plans 67 Sales Details 68 Report Switchboard 69 Finish 71 Input, Output and Processing Printouts 72 Input Screens 72 Available Stock 72 Customer Details 73 Delivery Appointments 74 Payment Plans 75 Sales Details 76 Switchboard 77 Report Switchboard 78 Splashscreen 79 Finish 81 Queries 82 Deliveries Query 82 Invoice Query 83 Old Deliveries Append Query 84 Payment Query 85 Stock Query 86 Outputs 87 Available Stock Report ...read more.
Middle
to store important documents outside the computer's hard disk which would help keep the information secure and safe in case of an in-store theft. However, this will be an additional cost to the user which may make his budget tighter than it currently is. Software: Software limitations include the user's experience and ability to use the software that will be required to run the new system that has been agreed. The user may not have any previous experience with the software that the system requires to run on so, he will have to be trained to use the system efficiently in order for it to benefit the company in the future. This will impose a cost factor on the user's budget as he may need to pay for the training unless someone offers to train the user without charging him. Also, a limitation of the software is that the user will have to purchase the software and pay licensing fees in order for it to work legitimately on the operating system. Apart from this the user shouldn't have any problems with implementing the system and using the software as it is compatible with the operating system that he already has. User: The user poses a limitation of the system, although he is competent in using a computer, his skills are somewhat basic. Therefore, the system has to be easy enough for him to use (as requested by him during the first interview). This consequently, has an effect on the design of the forms that the user will use once created. The forms that I have designed, and gained his approval of, seem to be as basic as possible. Apart form the end user's IT skills' posing a limitation, another limitation involves how much money the user has put aside and budgeted for this project. Seeing as the user has placed a budget on the amount of money he is willing to spend, the complexity of the database is subsequently been effected as well as ...read more.
Conclusion
out themselves when an overdue payment is approaching which extends the amount of work that the user has to do to find out about the overdue payments instead of reducing the amount of work that the user should have to do. Possible Extensions The possible extensions that could occur to the system involve removing the limitations that have been mentioned in the above section from the system. In order to remove the limitation of having to go to the deliveries report and finding what deliveries are due the next day, I propose that for future development an information message should appear the day before a scheduled delivery occurs on the opening of the system prompting the person working with the system to go to the relevant record and find out the exact details of the delivery so that they don't miss a delivery or don't leave out certain goods form the delivery which would hinder their future relations between the company and that particular customer. The other possible extension that could occur to the system is to remove the limitation of the user having to go to the "Out-standing Payments" report to find out about overdue payments and when the next payment for a particular customer is. In order to do so for future development, I propose that an information message appears on the opening of the system prompting the user to go to the actual report and finding out about the details of the payment plan arranged by the customer and the owner of the store. This would serve as a reminder to the company that certain customers still owe them money and that they should pursue those people for the overdue payments. Appendices Project Work: OCR ICT A Level Analysis Page: 2 Carlos Fernandes Project Work: OCR ICT A Level Analysis Page: 6 Project Work: OCR ICT A Level Analysis Page: 22 OCR ICT 2516 A Level Software Development and Implementation Page: 60 Project Work: OCR ICT A Level Evaluation Page: 122 ...read more.
This student written piece of work is one of many that can be found in our AS and A Level Information Systems and Communication section.
Found what you're looking for?
- Start learning 29% faster today
- 150,000+ documents available
- Just £6.99 a month