Information Technology for Pims Pumps Essay

abridgment constituent 1 Background/to identification of problem Pims Pumps argon an industrial pumping company which are involved in the distribution, inst t verboten ensemble(a)ation and maintenance of industrial pumping units. The company has a large fleet of vans and many specialised tools and lots of equipment. Currently e rattling(prenominal) of the equipment is logged in and out of the workshop and vans and this information is lineaged on paper.Analysis variance 2 identification of the prospective exploiter(s) The prospective drug exploiters are the managers of the business al bingle(prenominal) of whom are computer literate and are already using a computer dodge for other aspects of the business. The company concur a dinky network of computers inst altogethitherd and on the whole involved are competent in initiation and using Microsoft feeler 2000Analysis part 3 identification of exploiter wants and accept able limitations The dodge needs to be able t o descent large make outs of selective information about the whereabouts of equipment, it must be able to look through the info for any specified criteria, it must be able to be edited, it must be secure and utilizer fri dyingly.Inter becharm causa documents from userObservationThe proposed ashes shag only be time-tested to a certain extent on being able to store large amounts of dataAnalysis section 4 realistic estimate of the feasibility of potential solutions.Analysis section 5 justification of elect solutionI make water chosen to use this system becauseAnalysis section 6 description of watercourse system & data sources and destinationsThe current system involves the user logging in and out equipment to vans and back into the warehouse. The user must enter his/her name, the regard and time, the adjustment of the vehicle they are fetching it to, the name of the spell of equipment and the serial number of the minute of equipment. At the end of all(prenominal) we ek the logbook except for the most recent page is taken to the admin office and stored in a filing cabinet in date order. When a piece of equipment is missing, necessary of has been damaged the user can whence refer back to the log book to find out who if anyone serene has the piece of equipment and who else has apply it late. This can be very time consuming, as the user has to visually scan through the logbooks until he comes to the unveiling, which could be anything up to 15 pages. This could easily result in human error and is a big waste of timeAnalysis section 8 data flow plat of current systemAt current in that location is no flow of data as the information is simply logged and referred to if needed in the future.Analysis section 7 objectives of the projectInput tasks (Data en try on / Modification / View)The system allow provide a user-friendly simplified interface with the initial user allowing them to enter the same information as they usually do just on a lea rnboard. This should avoid all complications. The user interface for the initial user forget be very secure to try and prevent accidental damage to the system nevertheless the focal point features entrust be able to be accessed by the management team through a password. There volition be a user guide and a trouble shooting section to try and solve any potential problems. The system will be presented in form view with a main menu and various forms for assorted functionsOutput tasks (Reports)The system will be able to produce a report showing the location of any piece of equipment, or all the equipment one member of staff has recently used or all the equipment currently in a particular van. The system must be able to search through all the records for any criteria and produce a report for each oneProcessing tasksThe system must be able to process the information and sort it into any order that the user wishes.Quantitative performance considerationsThe system is going to be run everyplace a long period of time and so will need to be able to store a very large amount of data. This s one thing I will non be able to test to its full extent besides I can estimate through computer hardware performance whether the system is adequate or not.Qualitative evaluation criteriaData protective covering of the red-hot systemThe system will have security passwords and all obvious features that would allow the user to enter restricted areas of the system would be disabled. The system will barrack the user to save changes or automatically save changes on return anyway.Analysis section 9 Data flow diagram of new systemAnalysis section 10 E-R ModelProject coif 2 formula blueprint section 1 Overall system envisionThe system will involve a series of circuit cards, queries, reports and forms all linked together to provide a user-friendly system receptive of all of the system requirements. I will have tables for vans, equipment, warehouse and users and will link th ese together and display them on one form. There will be a menu form giving the user options and security passwords for management to access and edit existing data or to view existing data. All of the data entry will be pass and the tables will be set to certain data types to try and get word the user is entering the repair information. There will be intravenous feeding main tables cerebrate to qualifications, employees, equipment and vehicles. There will also be quaternary forms based upon these tables and then a main menu form for easy navigation of my database system program section 2 Description of modular structure of systemThe system will be based slightly 4 main tables. These are TblEmployees, which contains information about the employees that work at the company. TblEquipment, which lists equipment, details about it, its current location and a list of who has recently used it. TblVehicles will contain a list of all of the vans that Pims Pumps use and contain a list of all the equipment that is currently in each van. TblBookings will record all the interlockings in an out that a piece of equipment makes and records the equipment and employee ID numbers. These tables will all be linked together in an entity blood diagram. rule section 3 Definition of data requirementsThe database will have to store relevant information about the employees using the booking system information about the companys vehicles and equipment information. The fields I will store in my equipment table are as follows1. Equipment ID A uncommon number appoint to each piece of equipment.2. Description a truncated description of the piece of equipment3. Service interval The next date when the piece of equipment is due to be servicedThe fields I will store in my employee table are as follows1. Employee name full name of the employee2. Employee ID a unique number assigned to each employeeThe fields I will store in my vehicles table are as follows1. Registration The r egistration number of my vehicle2. Vehicle ID A unique number assigned to each vehicleI will also have a bookings table, which will store the employee and equipment ID for each booking of equipment, and the date on which the booking was made. This will enable me to run a query to find out for vitrine what equipment any employee has used or what equipment is currently in a certain van etc.Design section 4 naming of storage requirements and mediaDevelopment hardwareI can design my system on any hardware running Microsoft Windows 95 or ulterior and that is capable of running Microsoft vex at speed. I do not require any additional specific hardware for designing my database.End-user hardwareThe end user already has hardware capable of running my database and all the staff are familiar with Microsoft based programs.Development software productI will design the database in Microsoft Access as this is very whippy and powerful enough to undertake all or the required tasksEnd-user sof twareThe end user will also have to use Microsoft Access as that is the only program that my database will run on I will design the database to be user friendly and limit access to all of its functions to try and prevent accidental damage to the system.Design section 5 Identification of suitable algorithms for data transformationQueriesMacrosVisual prefatorial codeDesign section 6 identification of any administration requiredI have several input masks throughout my tables however no effectualations are needed. The input masks that ii have used are simply in place to ensure that the user is entering the clear up information or at least information that is in the correct format.Design section 7 overall user interface designHere is a plan of the layout of my main menuDesign section 8 Sample of planned data capture and entry (e.g. formsDesign section 9 sample of planned data validationDesign section 8 Description of record/database structure & normalisation calibrationTables d esignDesign section 11 Sample of planned valid output (e.g. reports)I will produce reports based on queries related to different things however the format will remain the same. Below is an example of what a report would look like if the user queried for what equipment an employee has recently usedDesign section 12 Database design including relations, foreign keys, and original keys.Entity-relationship diagramList and describe all relations separately1. There is a one to many relationship from Equipment ID in the Equipment table to Equipment ID in the booking table. This enables there to be many pieces of equipment logged in the bookings table.2. There is a one to many relationship from Employee ID in the Employees table to Employee ID in the Bookings table. This enables there to be many employees listed in the bookings table of that one employee can have many bookings.Indicate all primary and foreign keys for each tableTblEquipments primary key is Equipment ID and it contains no foreign keysTblBookings primary key is Booking ID and it contains Equipment ID and Employee ID as foreign keysTblVehicles primary key is Vehicle ID and it contains no foreign keysTblEmployees primary key is Employee ID and it contains no foreign keysDesign section 13 Planned measures for security and law of dataDesign section 14 Planned measures for systems securityDesign section 15 Overall test outlineProject submit 3 Technical solutionProject stage 4 strategy testing probe section 1- Design of test plan & strategy tally section 2 Minimal test data sort section 3 Expected results for typical test dataTest section 4 Erroneous data (Check forms reject invalid data)Test section 5 Expected results for natural dataCheck that data just within range is accepted and storedCheck that calculations using extreme data worksTest section 6 Hard sham of representative samples of test runsProject stage 5 keepMaintenance section 1 System overviewMaintenance section 2 compendium of features usedMaintenance section 3 -Sample of detailed algorithm design using a recognised methodologyMaintenance section 4 Annotated listings of program code, macro code & tailoringMaintenance section 5 Screenshots (Mainly from design view)Table backshotsReports screenshotsQuery screenshotsMacros screenshotsVisual canonical codeMaintenance section 6 List/description of pile items developedProject stage 6 exploiter manualUser manual Brief introductionUser manual Samples of actual screen displays in situUser manual Samples of error messages and/or error recuperation proceduresProject stage 7 AppraisalAppraisal section 1 Comparison of project performance against objectivesEvaluation of end-user requirementsEvaluation of the qualitative criteria