Functionality Statement
Table of contents
Contents
System design justification. 7
Summary of how I built this system.. 8
Functionality Statement
Level of achievement
Level 1
This report highlights completely the requirements as specified. The automated e-scooter database System has three basic tables. Relationships between the three tables are available and are both “one-to-many” types of relationships with enforcing referential integrity attribute checked. Functional queries are available and appealing forms. The forms have relevant titles, buttons, and text boxes. The system allows users to enter new record entries via the forms to the tables (Cheryl P. & Julia W., 2002).
Level 2
Every form, except the switchboard form, has a functional Combo box. There are numerous buttons with various functions. Some of the buttons available include “Back”, “Previous”, “Next”, “New Record” and “Save” buttons. Search functionality is available (David W., 2013).
Level 3
Every form has navigation aspects with the use of buttons. There is a form displaying borrowers’ details and age. A button to enable new loan entry is available.
Level 4
There is an option to delete or omit a record from the e-scooter database system. The system keeps records of every defaulter by the use of the overdue record. Attached is one of the reports available and is obtained from the system indicating Loan records.
Figure 1: a report indicating borrower records and loan statements.
General functionality
The level of functionality of this e-scooters automated system for keeping records is almost perfect. This is a prototype of the system for keeping track of loanees owing to scoot-e Company. The presence of tables present in the system facilitated the high functionality of the system as well as storing all record entries that are entered and need storage. Three tables are acting as the backbone of this MS Access system. The borrower table, borrowed scooters table, and e-scooters table.
The level of functionality of the system concerning the outlined Company’s specifications and requirements is almost a hundred percent, omitting the probability of little possible bugs in the system. Since this is a prototype version of a major system, the bugs are therefore subjected to debugging before a complete implementation phase into the workability application by the Company (Cheryl P. & Julia W., 2002).
Computations of arithmetic input and records are automated. The previous manual method applied is prone to several errors. The e-scooters automated system is therefore more accurate and timelier since the computation of operations is generally fast in all machine-related processing.
The system is more secure than manual record-keeping techniques since the system can be restricted and unauthorized access be controlled by the use of passwords and secret codes on Computers and laptops (Cheryl P. & Julia W., 2002).
User interface
The system has a switchboard user interface that allows the user to navigate with ease, between the available user interface forms. It is slightly tiresome and user-unfriendly to input data directly into the system tables (Cheryl P. & Julia W., 2002). To make this easier, each table has a user interface that is easily used to access and edit the stored data and information. The forms are appealing and they have buttons with a variety of functionality to make it easier to navigate and perform data editing functions of the system.
Search techniques
Combo boxes are available in every form to facilitate searching function. This saves time while looking for a certain set of the data entity. Combo boxes filter data and narrow down to the most specific data needed by the system user. This saves a lot of time considering that time is a scarce resource that can be converted into assets of the scooter-e Company (David W., 2013).
Data computation
By the use of queries that are linked together, data is executed more effectively and accurately to output correct information. The number of days a scooter is hired is obtained, the overdue time determined considering the day of return, and the total amount of loan that borrowers owe the scooter-e Company is computed by the use of queries and expression.
Information output
Reports are further released from the records entries and computed information. These reports will be printed if the need arise (Cheryl P. & Julia W., 2002). Reports are available to be viewed from the computer’s monitor as a soft copy. Reputations and Integrity of the Company remain high since loan information is computed and does not rely on a person’s decisions.
System design justification
The three tables are necessary to store loan information, borrowers’ details, and details concerning the scooters available to be hired. The tables are necessary for generating queries that are important as they compute data entered into the system (David W., 2013). Such computations include calculating the overdue days from the actual date/time a scooter is supposed to be returned.
The tables are linked to each other with the use of primary keys and secondary keys. The relationships facilitate reference between the independent tables with similar records (Cheryl P. & Julia W., 2002).
The system is functional and the buttons are working as expected. The Combo boxes are successfully performing search functions and tracking specific records. The reports give the computed information in a more appealing format that allows printing.
Entity relational diagram
The diagram below is a screenshot of the “one-to-many” relationships that link the three tables acting as the backbone of the e-scooters database management system.
Figure 2: a relationship diagram linking the three tables
Summary of how I built this system
The beginning point of every system is determining the entities required and the unique attributes that identify each record uniquely (David W., 2013). Assigning primary keys and secondary keys facilitated the relationships of the tables.
The tables give a chance of generating queries using the query wizard to select the most appropriate and correct data for execution. I came up with customized formulas where necessary.
I developed at least one form for every table. The forms are correctly titled and have buttons for easy navigation and data operations with a combo box in each form.
Reports show the records stored in the tables and computation outputs.
The last step is creating a blank form and creating navigation buttons to make it more user-friendly.
List of problems and bugs.
- Validating data entered into the system.
- Accuracy of contact address input still needs improvements.
- No VBA programming
- An aspect of regulating and balancing borrowers and loans/ scooters.
Reference
David W., (2013). An Introduction to Information Systems. Pp. 12-396.
Cheryl P. & Julia W. (2002). Develop and Use Complex Databases (Access 2002). Pp. 10-118.