Advantages And Disadvantages Of Web Databases Information Technology Essay

Advantages And Disadvantages Of wind vane Databases Information Technology EssayIn this chapter, the results of initial investigations and analysis carried out in order to determine the requirements that which is needed of the transcription by its future users, is outlined. Firstly, we take a look at the initial background research and its findings in relation to the topic. Secondly, this chapter then goes on to discuss the methodology and cultivation tools chosen to develop the application. Fin in ally, the requirements specification of the system is outlined including the users requirements both functional and non-functional that own been the guide in the development of the system.2.1 Background Research and AnalysisAs part of the initial stages of the project, investigations were carried out into the background of the topic atomic number 18a of web based applications since the application that has been create is in itself a web-based database application as advantageously as into the possible expectations and ineluctably that users would require of much(prenominal) a system. Besides research in various pieces of literature and the internet, informal interviews were also carried out with users of connatural known system, in order to get a better understanding of what users of such a system would come to expect as part of developing a requirements specification.2.1.1 Background Research FindingsWithin the last decade, the rapid evolution of the internet has opened the door for organisations to take advantage of its benefits as a way of life to improve their operating efficiency, lower cost and ultimately give themselves a competitive advantage over their competitors. Web based applications are increasingly existence used to handle tasks make by traditional applications such as data storage and transaction applications. With regard to data storage, ****Being web-based, web applications have significant benefits over their traditional counterpart s but with being web based also come many challenges for developers due mainly to their dynamic nature. This is due to promptly changing technologies, frequent changes of user requirements, and dynamic aspects of the software technologies (Wu Offutt). In development of these applications, developers must ensure that they are very reliable, exhibit very high usability as well as security (Wu Offutt). In comparison to their traditional software counterparts, web applications must be developed to be available at all times they must be maintainable given the rapid evolution of technology and most main(prenominal)ly, as they are based on the internet, they must be exceedingly scalable to facilitate a global market and ready to grow in terms of servers, services, and customers very quickly. (Wu Offutt)Web-based database applications, being web apps themselves, are no exception. The web as a platform for database systems according to Connelly Begg (2005) can deliver innovative solut ions for both inter- and intra- company business operations but also has its disadvantages.Advantages and Disadvantages of Web Databases according to Connelly Begg(2005)AdvantagesDisadvantagesSimplicityThey are easy to develop, as HTML upon which they are based is easy to learn and use.Cross Platform supportBeing web-based, they are not confined to any particular OS platform as they are accessible via web browsers.StandardizationWith HTML being a stock on all browsers, HTML documents can be read from any machine in the world.Scalable DeploymentReliabilityThe internet is menstruumly an unreliable and dumb communication medium. At times servers can be down and a message may be delayed to be sent. Also at pinnacle time when its is significantly slow.SecuritySecurity is of great concern especially when the organisation makes its databases accessible on the web.CostLimited Functionality of HTMLSome highly interactive database applications may not be converted easily to web based app lications, while still providing the same user friendliness.2.1.2. Problem Analysisestablish on observations from the daily operations of the MIS department with regard to problem tracking, the basic operations can be summarized as shown in the rich picture to a lower place*******2.1.3. Interview AnalysisDuring the investigation carried out, informal interviews were carried out with individuals who interact with similar systems to the one proposed. The questions used in these interviews can be found in supplement A. Both individuals who were interviewed use web-based help desk applications that are installed on their respective companys network as an application accessible via web browsers. See figure 1 to a lower place for a screenshot of one these applications.FIGURE 1Unicenter ServicePlus A web based help desk application used by one of the technicians interviewed.While these users describes these********************2.2 Development methodologySelection of the most appropriat e methodology for development is important for the success of the project. This is due to the fact that using an inappropriate methodology can lead to issues such as cost overruns as a result of poor project management, project incompletion or the development of the wrong functionality to incorrect specifications. The methodology selected for the development of the system would be the Systems Development Life Cycle (SDLC). This methodology was selected because it is one of the most stable methodologies with minimum risk. Also, the development approach to be used would be that of the falls Life Cycle model which is ideal for inexperienced developers. (Weaver 2004) It was also selected due to its simplicity.The system was modelled with the use of ER Diagrams as well as Use fount diagrams. Use case diagrams were used as they are one of the best modelling tools that give an idea on how the system will operate in relation to how the users would interact with it. It also gives a clear id ea of who the users of the system would be and the various views.2.3 Development ToolsCrucial to the development of the application, is the selection of the right programing tools. As such, since the application is a web-based database solution, it was necessary to select the software tool that could be best used as the foundation for the web-based database. The database tools considered were MySQL, MS Access and seer Database 10g Express. The table below shows a comparison between these three-In the end, the database tool selected was Oracle Database 10g Express Edition which was chosen because of its ease to use and learn. other plus to this application is its web readiness which makes it easy to host online, a crucial requirement for the application once completed. The downside******2.4 Requirement SpecificationThe system was developed to support 3 levels of users, namelyManagersGeneral drug usersTechniciansEachFunctional RequirementsAccording to Weaver(2004), Functional requ irements are those that define in some detail what the system needs to do. The functional requirements from the users point of view are as followsThe General user or Employee should be able to-Register and Login using Username and war cry Authentication get a problemView Solved ProblemsChange and Update personal informationThe Technical Support Manager should be able to-Login using Username and rallying cry AuthenticationView and reply to ProblemsAssign Problems to TechniciansAdd, Update or Delete System UsersView solve problems and add remarksAdd or Update provider informationView Technician detailsReview Resource HistoryReset User PasswordsView jobs DoneThe Technician should be able to-Register and Login using Username and Password AuthenticationSearch and View Problems AssignedView Jobs doneView Work QueueAdd, Append, Delete Job HistoryRecord Work doneUpdate personal informationChange passwordOther Functional Requirements include-DataThis is the lifeline of the system and is th erefore one of the most important aspects of the system. The data that the system would use are-Resources (allocated Hardware and Software) and their unique information such as its serial number, date of purchase, supplier, license details (for software resources), current location (a room number) and the resource symbol (e.g. Hewlett Packard T540 Imaging Package, or Microsoft Windows XP Professional 2002 Service Pack 1).Problems reported by EmployeesInformation recorded once a job is complete by a technician.ProcessingThis includes the processing of problems reported by Employees, and the allocation of jobs to Technicians based on the problems by the Technical Support Manager.User InterfaceAccording to Weaver (2004), the user interface of a system should be SimpleMade for the UserConsistentNon-Functional RequirementsAccording to Weaver(2004), non-functional requirements describe the instruction execution and constraints that the system should meet. The non-functional requirements areUsability The user interface must be consistent and user friendly while ensuring maximum efficiency while users navigate by means of the application.Availability the system must be available at all times during working hours.Access Users would be restricted according to their user type or level. Users will require a Username and Password to access the system.Capacity the system must be capable of holding large volumes of data, specifically complaints as well as solutions.