Information Technology for Pims Pumps Essay

Analysis percentage 1 Background/to identification of problem Pims Pumps be an industrial pumping comp every last(predicate) which are involved in the distribution, installation and brinytenance of industrial pumping units. The company has a large fleet of vans and umpteen specialised tools and lots of equipment. Currently all of the equipment is logged in and out of the store and vans and this study is stored on paper.Analysis contribution 2 identification of the prospective intentionr(s) The prospective drug exploiters are the managers of the parentage all of whom are computer literate and are already victimization a computer governance for other aspects of the business. The company have a small network of computers installed and all involved are adapted in opening and victimisation Microsoft access 2000Analysis parting 3 identification of user postulate and accept fit limitations The carcass penurys to be equal to store large amounts of info about the where abouts of equipment, it mustiness be sufficient to search through the data for any specified criteria, it must be able to be edited, it must be secure and user fri extirpately.InterviewExample documents from userObservationThe proposed schema usher out only be campaigned to a current extent on being able to store large amounts of dataAnalysis discussion section 4 realistic appraisal of the feasibility of potential solutions.Analysis section 5 justification of chosen solutionI have chosen to use this constitution becauseAnalysis section 6 description of current schema & 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 date and time, the accommodation of the vehicle they are taking it to, the name of the piece of equipment and the serial number of the piece of equipment. At the end of each(prenominal) week 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, postulate of has been deteriorationd the user can then refer back to the log book to find out who if anyone still has the piece of equipment and who else has utilize it lately. This can be rattling time consuming, as the user has to visually scan through the logbooks until he comes to the entry, which could be any function up to 15 pages. This could easily result in human error and is a uncollectible waste of timeAnalysis section 8 data flow diagram of current systemAt current there is no flow of data as the info is simply logged and referred to if needed in the future.Analysis section 7 objectives of the projectInput tasks (selective in arrangeion entry / Modification / View)The system leave provide a user-friendly simple interface with the initial user allowing them to enter the same information as they usually do just on a makeboard. This should avoid all co mplications. The user interface for the initial user pass on be very secure to try and prevent accidental damage to the system however the management features volition be able to be accessed by the management aggroup through a password. There will be a user guide and a fretfulness shooting section to try and solve any potential problems. The system will be presented in form view with a main notice and various forms for different 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 criminal 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 red to be roll over 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 not be able to test to its full extent however I can estimate through hardware performance whether the system is adequate or not.Qualitative evaluation criteriaData security of the new systemThe system will have security passwords and all unmistakable features that would allow the user to enter restricted areas of the system would be disabled. The system will prompt the user to save changes or automatically save changes on exit anyway.Analysis section 9 Data flow diagram of new systemAnalysis section 10 E-R ModelProject be 2 design purport section 1 Overall system designThe system will involve a series of gameboards, queries, reports and forms all linked together to provide a user-friendly system capable of all of the system requirements. I will have bows for vans, equipment, warehouse and users and will link these together and display them on one form. There will be a menu form braggy the user options and security passwords for management to access and edit lively data or to view existing data. All of the data entry will be legitimateated and the put offs will be set to certain data types to try and ensure the user is enter the correct information. There will be tetrad main prorogues related to bookings, employees, equipment and vehicles. There will also be four forms based upon these tables and then a main menu form for easy navigation of my database systemDesign section 2 comment of modular structure of systemThe system will be based around 4 main tables. These are TblEmployees, which encloses 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 bookings 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 affinity diagram.Design 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 unique number appoint to each piece of equipment.2. Description a brief description of the piece of equipment3. Service interval The following 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 adaption number of my vehicle2. Vehicle ID A unique number assigned to each vehicleI will also h ave 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 example what equipment any employee has used or what equipment is currently in a certain van etc.Design section 4 Identification of storage requirements and mediaDevelopment hardwareI can design my system on any hardware running Microsoft Windows 95 or later and that is capable of running Microsoft Access 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 acquainted(predicate) with Microsoft based programs.Development softwareI will design the database in Microsoft Access as this is very flexible and powerful enough to undertake all or the required tasksEnd-user softwareThe 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 basal codeDesign section 6 identification of any cogent evidence requiredI have several stimulant drug masks throughout my tables however no validations are needed. The input masks that ii have used are simply in place to ensure that the user is entering the correct 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 & normalisationNormalisationTables designDesign section 11 Sample of planned valid output (e.g. reports)I will produce report s 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 primary keys.Entity-relationship diagramList and pull back 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 Employe e 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 integrity of dataDesign section 14 Planned measures for systems securityDesign section 15 Overall test strategyProject salute 3 Technical solutionProject coiffure 4 System examen strain section 1- Design of test plan & strategyTest section 2 minimal test dataTest section 3 pass judgment results for typical test dataTest section 4 Erroneous data (Check forms reject invalid data)Test section 5 Expected results for extreme dataCheck that data just within range is accepted and storedCheck that calculations using extreme data worksTest section 6 Hard copy of representative samples of test runsProject stage 5 MaintenanceMaintenance section 1 System overviewMaintenance section 2 Summary of features usedMaintenance section 3 -Sample of detailed algorithm design usin g a recognised methodologyMaintenance section 4 Annotated listings of program code, macro code & tailorMaintenance section 5 Screenshots (Mainly from design view)Table screenshotsReports screenshotsQuery screenshotsMacros screenshotsVisual basic codeMaintenance section 6 List/description of package items developedProject stage 6 User manualUser manual Brief introductionUser manual Samples of essential screen displays in situUser manual Samples of error messages and/or error recovery proceduresProject stage 7 AppraisalAppraisal section 1 Comparison of project performance against objectives valuation of end-user requirementsEvaluation of the qualitative criteria