The Scope And Limitation Of The Study An Example

The Scope And confinement Of The Study An ExampleThe current traditional champion desk mechanisms used in UUM-CAS graduate(prenominal) alleviate angiotensin converting enzymeself desk discussion section at UUM atomic number 18 no long-dated enough to accommodate the increase of the moveions among the users and the technological delay employees because at that place is no standard and organized litigate at for use the users requests. This paper proposes a good financing clay that bum confront on students, round and make up lecturers at UUM Postgraduate CAS discussion section to freely interact with the node utility employees by cooking their requests and inquiries by dint of a weathervane- bumd do desk brass. In the oppo situation side, this proposed frame go a representation also increase the resultivity of the employees of the customer armed form discussion section since apiece specific tag end or line of work get out adoptd by a s pecific root of the skillful persist employees. In piece to pass on that , we ar passage to use a task track proficiency . This technique de crack up en qualified the users (students, mental faculty or lecturer) to trip out their inquiries to the ripe person in the customer back up discussion section. Also this technique go forth aim to track the enigma or slating of the users until it gets their direction to the proper person of the customer sink employees who bequeath soften to solve it indoors a convenient clipping.CHAPTER 1 origination1.0 BackgroundNowadays, a technical acquit service plays a principal(prenominal) role in a Universitys exponent to assist their students , staff and lecturers who rattling need or so study and technical leap out guides. In the retardation , Educational institutions face the challenge of providing technical back to faculty, staff, and students for firmness of aspireing their dubietys and resolveing to their inqu iries and riddles with a suitable resolves and within a convenient time. (Cruess, 2002 and Niedzwiecki Peterson, 2002). Moreover, The main goal of customer service is to proffer better overall service to the customer when they mite the customer service employees, either through electronic mail, or a visit call. We necessitate to make reliable that every superstar is satisfied with the beginning dissolve they birth with a correct solution in a timely manner. We want to be proactive and resolve as m whatsoever issues as we peck out front the customer even nonices that somewhat thing may contrive g superstar wrong. The customer should notice an improvement in the turnaround time when a ease request is submitted, as well as a reduction in the number of times they seduce to ask for help oneself until he/she gets the solution. (Schauer Thompson, 2004).This proposed determine give make an put upment in the current technical shop at mechanism used by the UUM Postgr aduate technical stake incision. It depart be conducted fundamentd on caper Tracking Technique which help to ensure consistent and part underpin, track the in diversenessation and tasks that come about into the champion Desk and decl atomic number 18 or forward the problems to the appropriate ready root and follow-up to make sure the problems were corrected.Problem statementPreviously, by apply the traditional help desk tools, the net interface was just a simple(a) interface with an engine for generating an netmail to our harbour staff. When an e-mail is sent to the electronic mailprotected for example, different staff testament receive it. This sometimes resulted in duplication of work since multiple people could work on the equal shred or email, or no sensation would handle it since some sorts would assume another(prenominal) groups or individuals would be handling a plastered email. T here(predicate) was no standard and organized process for handling the users requests. Sometimes no one responded even off away and other times multiple people did, showing that we were not very coordinated. The resembling thing happens when use a traditional yell call as a tool of communicating with the customer service (Schauer Thompson, 2004). Also Recently, in that respect pass water been increasing number of inter legal actions between users and customer service employees online. and so employees must take great deal of time to process inquiries from customers through the Internet (Iwai, Iida, Akiyoshi Komoda, 2010).In this query we atomic number 18 button to concentrate on the UUM Postgraduate CAS department to be as a domain of our landing field. In the meanwhile, students, staff and lecturers at UUM Postgraduate CAS department have always been able to submit problem reports via e-mail, or by bring forward. That is still true, but the question is How effective is the use of these tools? In fact , The current campus help desk has start out the hub of stand up with the mevery an(prenominal) spokes of user operate centered on it (Cruess, 2002). Students, staff and lectures do not have to be waited and passed on from one technical support employee to another until they get the answer of their problem or inquiry. In tack onition, once the student sends his/her problem to the help desk department by email , it will take long time until it gets puzzle out. Because the ticket will not send immediately to the proper person that he/she is aware of the problem that has already been sent .In this case, the number of times that they have to ask for help will increase .As a consequence, and base on the points that we mentioned previously, we proposed a web- found help desk clay that flock be used as a bridge between the users (students, staff, lecturer) and the technical support employee at UUM Postgraduate CAS department. In order to go forth consistent and quality support to the students, staff and lecturers. In the proposed carcass we are going to use a problem tracking technique to track the information and problems that come from the customers into the Help Desk. In addition, assign or forward the problems to the appropriate workgroup and make sure that the problems are solved.enquiry QuestionsBased on the problem statement mentioned in the first place, the following questions are constructedWhat are the Limitations of the current UUM Postgraduate CAS help desk ashes?What are the techniques that we are going to use during the growing stage of the double of Postgraduate UUM help desk carcass?How can we evaluate the effectiveness of the proposed carcass?Research ObjectivesThe main nonsubjective of this study is to enhance the current technical support of UUM Postgraduate department by developing an organized and solid web-based technical support system based on a problem tracking technique. In order To achieve this main objective, some sub-objectives can be formulatedTo some (prenominal)ise limitations of the current help desk system.To design and develop a icon web-based help desk system based on problem tracking technique.To evaluate the prototype web-based help desk system based on problem tracking technique among the users.Significance of the studyThe proposed model will provide a significant and flexible way of communicating between the customer service at UUM and their users. Here are some significant and beneficial achievements that the proposed system is anticipate to provideThe system can assist the students in postgraduate department to find the solutions for routine questions through FAQ part and sleep with its requests by utilise problem tracking technique.The system will help the university to build a strong relationship with their students.Increase the productivity of the employees at work and provide faster and more convenient function to their students, staff or lecturers. all(prenominal) the users requests will directly send to th e proper department of the customer service for finding a solution instead of sending all requests to one customer service department and consequently this department will try to find the suitable person who can answer the incoming request, and here we waste the time.Thus, we expect from this system to enhance the previous customer services tools and make it more effective and organized.Scope and limitation of the studyThis study will focus on developing a web-based help desk system victimization a problem tracking technique for Postgraduate UUM-CAS department at UUM. This system will let users (staff, students or lecturers) to freely interact with the technical support employees who have the ability to answer all problems think to the postgraduate services provided by the UUM-CAS. In addition, UUM-CAS postgraduate students can sail FAQ section which contains a groups of frequently asked questions that are related to UUM-CAS Postgraduate department at UUM and they can find their problem or inquiry thither. Moreover, the proposed system will help the students, lecturers, and staff at UUM-CAS postgraduate department to happen the latest UUM-CAS postgraduate word of honor and articles added by the technical support employees. The prototype to be develop is based on problem tracking technique. shaping Of The ReportThis report consists of six chapters which will cover the designing and the developing online help desk system for UUM-CAS postgraduate department at UUM. Here is an overview of the circumscribe of each presented chapterChapter One this chapter introduces the problem, gives an overview about the study and describes the call for of help desk systems in the educational sectors. This chapter also discusses the scope of the study, the significance of the study and its objectives.Chapter Two this chapter covers the writings review which is the previous related works that been make before. Moreover, this chapter represents relevant information for u nderstanding the study more.Chapter Three this chapter explains the details of the selected methodological analysis that we are going to use in the project.Chapter Four this chapter discusses about the prototype development and the carrying out of the online help desk system for UUM-CAS postgraduate department at UUM.Chapter Five this chapter discusses the valuation process of the proposed help desk system.Chapter Six this chapter discusses the conclusion, recommendations and future works to improve this study.CHAPTER devilLITERATURE REVIEWIntroductionThis chapter discusses the relevant help desk researches that had been done before by researchers. Moreover, this chapter presents the current techniques used by UUM-CAS technical support department also it presents the techniques that we are going to use in the proposed study including problem tracking technique. In addition , it discusses the previous researches that had been done before using this techniques.Definition of Online Help Desk bodyOnline helpdesk as outlined by Donna Knapp in a Guide to Customer Service Skill and Helpdesk Professional is a exclusive point of contact within a company for managing customers problem and request and providing solution oriented support services (Knapp, 2009). Online help desk is also define a Help Desk as a formal arranging that provides support functions to users of the companys product, services, or technology (Wooten, 2001). other explanation has been defined by Albin who said Technical support is a service. Its about assisting pertaining to technology, especially regarding computers. It is also has to do with providing acceptable, effective and efficient resolutions(Albin, 2002). As a consequence, Helpdesk is usually k right offn as a department within a company that responds to users technical questions or inquires.Background of Online Help Desk oftentimes the term Helpdesk is used for internal support within the organization or for external support groups . Educational Institutions need to provide spirited quality of customer service and support to respond to the users inquires and problems within a convenient time . A well designed Help Desk product should have the ability for the support customer to be part of the solution by offering a searchable acquaintance base of third estate support issues and questions and a way for customers/users to easily create their own support tickets. With a web based interface, most users are able to navigate simple web forms with fairly high success rates to submit a trouble ticket or find answers to frequently asked questions or common problems. The helpdesk is responsible for bringing an organizations resources together in order to provide its customers with quality support and service (Czengel, 2001 and Vanderlip, 2004). Thus, to be able to choose the right techniques and to use them effectively in the help desk system, you have to understand what customers want. wise(p) this will help you ma ke sense of the techniques youll be looking at (Bacal, 2005).Benefits of Online Help Desk SystemWeb-based support offers an extremely wide variety of benefits. These will vary depending on factors much(prenominal) as the generation of the support site, the tools employed, the write of the customer base, the services offered, and so on. Benefits typically originate from dickens aspects of supportSelf-serviceSingle source accessThe benefits of self-serviceOn a Web-based support site, self-service refers to all information, functions, and services that customers can take favor of on their own, without having to contact a support representative. users might view or download information or seminars, search for solutions in a knowledge base, download a software upgrade, or check on the mature of their support log. The primary benefit of self-service is the ability to offer customers some form of support 24 hours a day, seven days a week. These extended hours of support come at no ad ditional cost. The self-service functions you offer on your site would be available around the clock. Another significant benefit of self-service is the reduction in calls to the staffed support area. This agency the more calls you are able to divert from your support area to your Web-based support site, the more benefits you will gain. This can achieved by laying FAQ part in the system which contains the most frequently asked questions which eat up most of technical support employees time (Czengel, 2001).The Benefits of Single Source retrieveA Web-based support site that contains documents such as Knowledge base, FAQs, News, and so onThis documents will provide users with a single source access to the service provided by the prove or the organization. Implementing Online Helpdesk System, management can have a single point of contact with the users and resolve their problems (Czengel, 2001).In addition to the two benefits that we have mentioned before there are some other all i mportant(predicate) benefits of using Online Helpdesk Systems and they are as followsImproved help desk service quality as all inquiries or problems are immediately taken action timely identification, diagnosis and resolution of problem Improved user or customer satisfaction.Providing existing users or customers with knowledge and FAQs (Frequently Asked Questions) concerning the educational institutions services.24-hour availability which factor that the system is available always to receive the problems or inquiries from the users at any time and in any day.Troubleshooting features gives users or customers the ability to solve many support problems on their own.This tool provides the users or customer with an easy way of connecting with the technical support employees and within a convenient time.Serves as a tool for tracking and recording helpdesk inquiries, which provides a knowledge base of resolutions to previous calls concerning similar issues.The Potential Pitfalls of Web-ba sed SupportThe potential pitfalls in Web-based support come from poor planning and implementation. A site that offers little true(a) value to the customers or users, no matter how visually perfect it is, is worthless. Sites that are difficult to navigate, that contain out-of-date information, that do not offer help for the most common problems, that are designed at too locomote or too simple a level for the customer base they support all fall into the worthless category. You can spend a fortune on support tools, but if you havent done a arrant(a) job in planning and implementation, your support site will give and you will get no payback on what you invested. Customers/users will go to alternatives such as telephone support, and getting them back to the Internet would be difficult (Czengel, 2001).Web-Based ApplicationWeb covering known as an online discourse services that client can access through their computer or handheld devices, this communication can be optimized via net support such as the Internet or an intranet (Grove, 2009).Problem Tracking Technique in that location are many researches had been done before using a Problem Tracking Technique. This technique had been used in order to improve the expertness of using help desk systems by the users. One of the research that had been already done is a help desk system that had proposed for The Information Technology Services surgical incision in North Dakota State University . The system allows them to track problems by delegate person, assigned group, for a specific user and many other ways. They can generate ad hoc reports to analyze problems that have occurred over a set out stage of time or by department as needed. Thus, For a help desk to be effective and efficient, it needs to have a proper set of tools. These tools are used to manage the incoming calls, monitor servers and network unions, track problems as they enter the help desk and are transferred to other support units, being able to v iew the end users screen, documentation, training and many others.User PartOnce the user did not find the solution of his /her problem in the FAQ part, he/she is going to use the ticketing system which is one of the system functionality. The user will create a new ticket and hold his/her inquiry or problem within this ticket. The process of creating new ticket includes several pure tones. At the beginning the customers must choose the section that the go about problem belongs to. For example students fees section or registration section. After that, the customer will enter his/her personal information and he can specify a priority to his/her ticket for example urgent or prevalent .The customer can attach a file with his/her ticket in order to explain his/her problem more (Edwards, 2010 and Kayako, 2009).Technical support employees partAfter the user completes the process of sending his/her ticket to the suitable group of the technical support employees, here comes the role of te chnical support employees to respond to this ticket . all(prenominal) ticket has a status which can be diffuse, wait for reply or Closed .Once the user creates his/her new ticket and sends it to the technical support employees, the status of his/her ticket will be automatically Open since it is a new ticket. Thats mean it needs a reply from the technical support employees. After one of the technical support employees replies this ticket, he/she will diverge the status of this ticket to be Waiting for reply which direction the ticket has been replied by the suitable technical support employee and its status now is Waiting the user to send another reply if the first answer that he/she already got is not clear enough. Suppose that the customer needs more explanation or more details about his/her problem, wherefore after he/she got the reply from the customer service, the user can metamorphose the status of this ticket from Waiting for reply to be Open and send it again with his/he r new inquiry to the customer service employees. The status of the ticket will automatically belong closed after a period of time called out-of-pocket which is specified by the administrator of the system and it is defined as the maximum time that the ticket will be remained in case of waiting for a response from the user. That means after the deviation of this time, the status of the ticket will be closed. After this time called DUE the ticket will be closed and it will become as a read-only ticket from the side of users. In other words, the problem has been solved and does not need any reply anymore. The last thing that we want to indicate that imagine that a user has sent a ticket to the technical support employees through the system and lets answer this question what will happen if the ticket still in the queue of the tickets queue without any answers from any technical support employee? In fact this case is the mop case that it might make the user in the status of waiting f or reply through unlimited time. In order to handle this problem, In the proposed system there is a part for administrators which enable the help desk managers or administrators to monitor and manage the process of ticketing system. They can view the tickets that no one has answer it and assign it to the suitable technical support employee. (Edwards, 2010 Schauer Thompson, 2004 and Kayako, 2009).Building up FAQBuilding up FAQ is also an important task of help desk. The purpose of building up the FAQ is to reduce the number of inquiries that come from users. Users can order the FAQ pages and clear up their unfamiliar matters before they send emails or tickets to the help desk employees. Help desk employees also can analyze inquiry records, construct questions and add them to the FAQ part. For example, if the help desk employees see that there are questions that come out from users several times, then they can simply organize these questions by added them to the proper group of FAQ section so the users can find it there before they send a new question which is already exists at FAQ section (Iwai, Iida, Akiyoshi Komoda, 2010 and Kayako, 2009).UUM-CAS help desk mechanismsIn the meanwhile, the current technical support mechanisms used by UUM-CAS postgraduate technical support department are still limited to phone call and email as a way of communicating between users and the technical support employees. Generally, the disadvantages of using this current techniques are divided into two parts based on email or phone call. The first part of disadvantages are the problems of using phone call as a tool of providing the technical support service. The first problem of using the phone call is that the technical support employees are not always the same who answer the phone. Which means, every time you talk to different technical support employee, you should explain your problem again and again until you get the solution of your problem. The cooperate issue of using a p hone call is the wasted time that the user should wait since he/she may pass on from one technical support employee to another until he/she gets the answer of his/her problem or inquiry. The third issue appears during the registration time while the pressure on the technical support center is more comparison to other time and especially on using phone call. At that time, the user should wait on the phone until he/she can talk to the customer service employees since the phone is busy. From the other side, there are some issues comes from using the email as a way of interacting between the users and the customer service employees. starting line of all, it takes long time from the customer service employees side until they solve the issues since the problem will not be received from the proper technical support employee who has an infrastructure about the problem that had been sent by the users. The second thing is multiple people could work on the same email or no one would handle it since some customer service employees will assume that other employees would handle it. Thus, and as we can see there is no standard and organized way of handling with the users inquiries and problems.Chapter SummaryThe abstract of literature review had broadened the scope of Online Helpdesk issues. The information and findings collected form this chapter is used as a guidance to develop the Online Helpdesk system. By reviewing the UUM-CAS postgraduate help desk case study, we can conclude that helpdesk system plays an important role in the educational institutions. This chapter has also demonstrated the vastness of helpdesk system in the context of UUM-CAS postgraduate help desk department.CHAPTER 3RESEARCH METHODOLOGYIntroductionThis chapter discusses the adopted methodology which applied to achieve the objectives of the study in designing and developing the proposed web-based help desk system for UUM-CAS help desk department.Research MethodologyResearch methodology plays a ver y important role to proceed and carry out with the whole all research study. Moreover, it is very important to choose the suitable methodology for your study in order to achieve the objectives of the study. In general, a lot of studies that had been done before use the research methodology to achieve many purposes such as gathering entropy and information, development and evaluation (Refsdal, 2008 Schmuller, 2002). Besides that, Research methodology step makes us fully awareness about the requirements of our study and the problem statement of the research. Thus, The methodology of this research the we are going to apply is based on the five general research steps that are proposed by Vaishnavi Kuechler. These steps includes the awareness of problems, suggestions, development, evaluation, and the conclusion of the research as they are illustrated in the Figure 3.1.The awareness of problemsIn this step, some important information had been gather about the current problems and limi tations of using the current traditional help desk mechanisms at UUM-CAS help desk department. This can be achieved by interviewing the students, lectures, and staff to see what are the disadvantages of using the current customer service in order to cut across it. Moreover, we can use some beneficial instruments such as questionnaire. In addition, we can collect some information from some related work that had been done before by other researchers. Thus, This step aims to identify the problems and come out with a significant and more organized solution.SuggestionsThe second step of the methodology of this research is to suggest building a web-based cover based on problem tracking technique in order to enhance the current technical support tools used by UUM-CAS help desk department. In this phase, some flow charts and some Unified Modeling Language (UML) diagrams will be used to design the proposed prototype. The Figure 3.2 illustrates briefly the technical support operation of the proposed systemFigure 3.2 Diagram explains the proposed system Design recipeDesign patterns describe how objects communicate without become entangled in each others data models and methods. Keeping this separation has always been an objective of good OO programming, and if you have been trying to keep objects minding their own condescension, you are probably using some of the common design patterns already (Cooper, 2002). wherefore Design Pattern?Why do we need to use design pattern? Nowadays computers programs is sightly more complicated, for this reason it is important to have a way of qualification building software easier and less complexity. For example, SQL Server and Oracle are become the most common databases used in the meanwhile . Lets imagine that we are working in a software company and we already developed a costly system using SQL Server database and because of a certain reason the company wants to change its database server into Oracle. Does that mean we want to sheer everything has been built and start building our new system from scratch? The answer is no of course. By using a design pattern we will be able to build a system which rebuilding ability exists. As a result, we just need to change the part of recruit which deals with SQL Server with Oracle one. Design pattern has divided the system into point each storey has its own job starting from the View horizontal surface and ending with the database layer and the externalise 3.4 below is really express what i just mentioned.If we ignore using design pattern in our system , then our system simply will miss the usability technique. As the figure 3.5 shows that we should not ignore the Business tier and dealing directly with the data tier if we do so then it is hard to make changes in the application. Thus, In this case and if we want to change in one place, then we should change in many other places that are related to the change instead of make the changes in one place by using th e organized design patterns.To explain how does the design pattern technique work, lets take the following scenario Once the system has started, it will collect some classs from configuration file about the connection string of the database and the name of Business logical system floor DLL (BLL). That means the connection with the database will not establish until the business layer successfully retrieved the configuration from the configuration file. Business Logic Layer is responsible for retrieves data from the data layer, so the business logic layer plays the role of mediator between presentation layer and database layer. IDAL (Interface Data Access Layer) is an interface that we just need to deal with it regardless the type of database that the system works with. Hardware Requirements Of The SystemSince the proposed system is a web-based application, so to run the system on the web milieu we need a web application server that can handle the requests that come from the users of the proposed help desk system. In addition to the web server, To run the system on the web server, it has to have the minimum hardware characteristics that enable the web server from installing pane of glass net features such as point in time net framework which is indispensable to run the application on the web server smoothly and successfully. packet Requirements Of The SystemAs we mentioned in the hardware requirements of the system, we need to install the dot net framework on the web server since the developing environment of the proposed system is Microsoft Visual Studio and this framework is necessary to run the application successfully on the server. Besides that, a web browser application is necessary to be installed which is the middle tool that will make the connection with the system application which is running on the server side. User Requirements Of The SystemGenerally, The user of the proposed system is divided into three categories. That is, UUM users (studen t and lecturer), technical support employee, and administrator. Each group of the system has its role based on its authority of using the system. Since the proposed system consists of three parts ( User, Technical support employee, Administrator) , each group of the users can use the suitable part based on their authority. UUM users can use the user part of the system to submit the problems as a tickets to the customer service employees. In addition, they can see the latest news and articles added by the customer service employees and download the files that are related to UUM-CAS. slice the technical support employees are responsible to respond to the tickets that come from the user part, in addition to manage the articles, news and download sections in the user part. The last part is the administrator which is responsible to manage the technical support part throw adding new group in addition to manage the technical support employees.DevelopmentA software development process is a process to build a software product or to enhance an existing one. Moreover, the Development stage of the research methodology is the most significant stage in our study since it represents the answer o