畢業(yè)論文-電信網(wǎng)上營業(yè)廳用戶自服務(wù)系統(tǒng)的設(shè)計與實現(xiàn)

1、 太原理工大學畢業(yè)設(shè)計(論文)用紙?zhí)砉ご髮W畢業(yè)設(shè)計（論文）任務(wù)書第1頁畢業(yè)設(shè)計（論文）題目：電信網(wǎng)上營業(yè)廳用戶自服務(wù)系統(tǒng)的設(shè)計與實現(xiàn)畢業(yè)設(shè)計（論文）要求及原始數(shù)據(jù)（資料）：1綜述國內(nèi)外網(wǎng)上營業(yè)廳研究現(xiàn)狀；2深入了解自服務(wù)系統(tǒng)的相關(guān)技術(shù)；3熟練掌握電信級別系統(tǒng)的應(yīng)用與分析，訓練編寫java程序的能力；4設(shè)計并實現(xiàn)網(wǎng)上營業(yè)廳服務(wù)相關(guān)模塊；5深入分析網(wǎng)上營業(yè)廳自服務(wù)系統(tǒng)的關(guān)鍵技術(shù)與編寫語言；6訓練檢索文獻資料和利用文獻資料的能力；7訓練撰寫技術(shù)文檔與學位論文的能力。第2頁畢業(yè)設(shè)計（論文）主要內(nèi)容：1綜述電信網(wǎng)上營業(yè)廳自服務(wù)系統(tǒng)在現(xiàn)實中的應(yīng)用；2了解自服務(wù)系統(tǒng)的相關(guān)技術(shù)；3熟悉電信網(wǎng)上營業(yè)廳自服務(wù)

2、系統(tǒng)以及插件的開發(fā)環(huán)境； 4設(shè)計漏洞掃描器中針對某一漏洞檢查的插件；5. 深入分析網(wǎng)上營業(yè)廳自服務(wù)系統(tǒng)的關(guān)鍵技術(shù)與編寫語言；6熟練掌握電信網(wǎng)上營業(yè)廳自服務(wù)系統(tǒng)的程序編寫；7設(shè)計并實現(xiàn)網(wǎng)上營業(yè)廳服務(wù)相關(guān)模塊。學生應(yīng)交出的設(shè)計文件（論文）：1內(nèi)容完整、層次清晰、敘述流暢、排版規(guī)范的畢業(yè)設(shè)計論文；2包括畢業(yè)設(shè)計論文、源程序等內(nèi)容在內(nèi)的畢業(yè)設(shè)計電子文檔及其它相關(guān)材料。 第3頁主要參考文獻（資料）：BruceEckel;JSP programming ideasJ;Machinery Industry Press;2003.1378賽奎春;JSP工程應(yīng)用與項目實踐J;機械工業(yè)出版社;2002.23294

3、 FLANAGAN;JSP Technical ManualJ;Electric Power Press;2002.1465孫一林,彭波;JSP數(shù)據(jù)庫編程實例J;清華大學出版社;2002.30210LEE ANNE PHILLIPS;learning and using JSPJ;Electronic Industry Press;2004.1319陳石;XML技術(shù)及其應(yīng)用J;計算機應(yīng)用研究;2002年03期耿祥義,張躍平;JSP實用教程J;清華大學出版社;2003.1354孫涌;現(xiàn)代軟件工程J;北京希望電子出版社;2003.1246王珊;數(shù)據(jù)庫系統(tǒng)概論J;高等教育出版社;2002.3460B

4、rown等;JSP Programming GuideJ;Electronic Industry Press;2003.1268清宏計算機工作室.JSP編程技巧J;機械工業(yè)出版社; 2004.1410朱紅,司光亞;JSP編程指南J;電子工業(yè)出版社; 2001.34307 專業(yè)班級軟件1014班學生要求設(shè)計（論文）工作起止日期2014年3月17日2014年6月27日指導(dǎo)教師簽字日期2014年3月17日教研室主任審查簽字日期系主任批準簽字日期ii電信網(wǎng)上營業(yè)廳用戶自服務(wù)系統(tǒng)的設(shè)計與實現(xiàn)摘要本文在對目前各種網(wǎng)上營業(yè)廳的功能原理進行了分析后，在山西省移動公司實習期間，為保證電信網(wǎng)上營業(yè)廳系統(tǒng)中心數(shù)據(jù)庫

5、的安全，設(shè)計了一個具有三層結(jié)構(gòu)的網(wǎng)上營業(yè)廳，以web頁面方式實現(xiàn)了與用戶的交互，同時保證了網(wǎng)上營業(yè)廳終端系統(tǒng)與中心數(shù)據(jù)庫的隔離。使用JSP編程語言作為開發(fā)工具實現(xiàn)了終端動態(tài)頁面的設(shè)計，提供了安全、友好、快速的訪問交互方式,提高了程序的靈活性和系統(tǒng)的安全性。整個系統(tǒng)能夠?qū)崿F(xiàn)話費查詢、業(yè)務(wù)受理的基本業(yè)務(wù)，同時還對交易中用戶的各種操作進行了記錄，擴展了意見反饋和手機號碼歸屬地查詢等網(wǎng)絡(luò)服務(wù)功能，通過了調(diào)試和試運行。但是這個系統(tǒng)還有很多不完善之處，需進一步升級改進。關(guān)鍵詞：網(wǎng)上營業(yè)廳；JSP編程；數(shù)據(jù)庫iiiiTelecom online business users to design and im

6、plementation of self-service systemsAbstractBased on the principle of online business hall is analyzed, during my internship in Shanxi province Mobile Corporation, in order to ensure the telecom online business hall system center database security, design a three layer structure of the online busine

7、ss hall, to the web page to realize the interaction with the user, and ensures the isolation net business office terminal system and central database. The use of JSP programming language as the development tool to realize the design of dynamic pages, to provide a safe, friendly, fast access to inter

8、active mode, improves the safety of flexibility and the system program. The whole system can realize the basic business calls inquiries, business acceptance, but also various operations on the transaction of users were recorded, extends the feedback and mobile phone numbers attribution to inquiries

9、and other functions of the network service, through the commissioning and trial operation. But the system there are many imperfections, need further improvement.Key words: Telecom online business; JSP programming; Database目 錄 TOC o 1-3 h z u HYPERLINK l _Toc19539 摘要i HYPERLINK l _Toc3242 Abstractii

10、HYPERLINK l _Toc31953 1.緒論 外文原文Java and the InternetIf Java is, in fact, yet another computer programming language, you may question why it is so important and why it is being promoted as a revolutionary step in computer programming. The answer isnt immediately obvious if youre coming from a traditi

11、onal programming perspective. Although Java is very useful for solving traditional standalone programming problems, it is also important because it will solve programming problems on the World Wide Web. What is the Web?The Web can seem a bit of a mystery at first, with all this talk of “surfing,” “p

12、resence,” and “home pages.” Its helpful to step back and see what it really is, but to do this you must understand client/server systems, another aspect of computing thats full of confusing issues. Client/Server computingThe primary idea of a client/server system is that you have a central repositor

13、y of informationsome kind of data, often in a databasethat you want to distribute on demand to some set of people or machines. A key to the client/server concept is that the repository of information is centrally located so that it can be changed and so that those changes will propagate out to the i

14、nformation consumers. Taken together, the information repository, the software that distributes the information, and the machine(s) where the information and software reside is called the server. The software that resides on the remote machine, communicates with the server, fetches the information,

15、processes it, and then displays it on the remote machine is called the client.The basic concept of client/server computing, then, is not so complicated. The problems arise because you have a single server trying to serve many clients at once. Generally, a database management system is involved, so t

16、he designer “balances” the layout of data into tables for optimal use. In addition, systems often allow a client to insert new information into a server. This means you must ensure that one clients new data doesnt walk over another clients new data, or that data isnt lost in the process of adding it

17、 to the database (this is called transaction processing). As client software changes, it must be built, debugged, and installed on the client machines, which turns out to be more complicated and expensive than you might think. Its especially problematic to support multiple types of computers and ope

18、rating systems. Finally, theres the all-important performance issue: You might have hundreds of clients making requests of your server at any one time, so any small delay is crucial. To minimize latency, programmers work hard to offload processing tasks, often to the client machine, but sometimes to

19、 other machines at the server site, using so-called middleware. (Middleware is also used to improve maintainability.) The simple idea of distributing information has so many layers of complexity that the whole problem can seem hopelessly enigmatic. And yet its crucial: Client/server computing accoun

20、ts for roughly half of all programming activities. Its responsible for everything from taking orders and credit-card transactions to the distribution of any kind of datastock market, scientific, government, you name it. What weve come up with in the past is individual solutions to individual problem

21、s, inventing a new solution each time. These were hard to create and hard to use, and the user had to learn a new interface for each one. The entire client/server problem needs to be solved in a big way. The Web as a giant serverThe Web is actually one giant client/server system. Its a bit worse tha

22、n that, since you have all the servers and clients coexisting on a single network at once. You dont need to know that, because all you care about is connecting to and interacting with one server at a time (even though you might be hopping around the world in your search for the correct server). Init

23、ially it was a simple one-way process. You made a request of a server and it handed you a file, which your machines browser software (i.e., the client) would interpret by formatting onto your local machine. But in short order people began wanting to do more than just deliver pages from a server. The

24、y wanted full client/server capability so that the client could feed information back to the server, for example, to do database lookups on the server, to add new information to the server, or to place an order (which required more security than the original systems offered). These are the changes w

25、eve been seeing in the development of the Web. The Web browser was a big step forward: the concept that one piece of information could be displayed on any type of computer without change. However, browsers were still rather primitive and rapidly bogged down by the demands placed on them. They werent

26、 particularly interactive, and tended to clog up both the server and the Internet because any time you needed to do something that required programming you had to send information back to the server to be processed. It could take many seconds or minutes to find out you had misspelled something in yo

27、ur request. Since the browser was just a viewer it couldnt perform even the simplest computing tasks. (On the other hand, it was safe, because it couldnt execute any programs on your local machine that might contain bugs or viruses.) To solve this problem, different approaches have been taken. To be

28、gin with, graphics standards have been enhanced to allow better animation and video within browsers. The remainder of the problem can be solved only by incorporating the ability to run programs on the client end, under the browser. This is called client-side programming. Client-side programmingThe W

29、ebs initial server-browser design provided for interactive content, but the interactivity was completely provided by the server. The server produced static pages for the client browser, which would simply interpret and display them. Basic HyperText Markup Language (HTML) contains simple mechanisms f

30、or data gathering: text-entry boxes, check boxes, radio boxes, lists and drop-down lists, as well as a button that can only be programmed to reset the data on the form or “submit” the data on the form back to the server. This submission passes through the Common Gateway Interface (CGI) provided on a

31、ll Web servers. The text within the submission tells CGI what to do with it. The most common action is to run a program located on the server in a directory thats typically called “cgi-bin.” (If you watch the address window at the top of your browser when you push a button on a Web page, you can som

32、etimes see “cgi-bin” within all the gobbledygook there.) These programs can be written in most languages. Perl has been a common choice because it is designed for text manipulation and is interpreted, so it can be installed on any server regardless of processor or operating system. However, Python (

33、my favoritesee www.P) has been making inroads because of its greater power and simplicity. Many powerful Web sites today are built strictly on CGI, and you can in fact do nearly anything with CGI. However, Web sites built on CGI programs can rapidly become overly complicated to maintain, and there i

34、s also the problem of response time. The response of a CGI program depends on how much data must be sent, as well as the load on both the server and the Internet. (On top of this, starting a CGI program tends to be slow.) The initial designers of the Web did not foresee how rapidly this bandwidth wo

35、uld be exhausted for the kinds of applications people developed. For example, any sort of dynamic graphing is nearly impossible to perform with consistency because a Graphics Interchange Format (GIF) file must be created and moved from the server to the client for each version of the graph. And youv

36、e no doubt had direct experience with something as simple as validating the data on an input form. You press the submit button on a page; the data is shipped back to the server; the server starts a CGI program that discovers an error, formats an HTML page informing you of the error, and then sends t

37、he page back to you; you must then back up a page and try again. Not only is this slow, its inelegant. The solution is client-side programming. Most machines that run Web browsers are powerful engines capable of doing vast work, and with the original static HTML approach they are sitting there, just

38、 idly waiting for the server to dish up the next page. Client-side programming means that the Web browser is harnessed to do whatever work it can, and the result for the user is a much speedier and more interactive experience at your Web site. The problem with discussions of client-side programming

39、is that they arent very different from discussions of programming in general. The parameters are almost the same, but the platform is different; a Web browser is like a limited operating system. In the end, you must still program, and this accounts for the dizzying array of problems and solutions pr

40、oduced by client-side programming. The rest of this section provides an overview of the issues and approaches in client-side programming. Plug-insOne of the most significant steps forward in client-side programming is the development of the plug-in. This is a way for a programmer to add new function

41、ality to the browser by downloading a piece of code that plugs itself into the appropriate spot in the browser. It tells the browser “from now on you can perform this new activity.” (You need to download the plug-in only once.) Some fast and powerful behavior is added to browsers via plug-ins, but w

42、riting a plug-in is not a trivial task, and isnt something youd want to do as part of the process of building a particular site. The value of the plug-in for client-side programming is that it allows an expert programmer to develop a new language and add that language to a browser without the permis

43、sion of the browser manufacturer. Thus, plug-ins provide a “back door” that allows the creation of new client-side programming languages (although not all languages are implemented as plug-ins). Scripting languagesPlug-ins resulted in an explosion of scripting languages. With a scripting language, y

44、ou embed the source code for your client-side program directly into the HTML page, and the plug-in that interprets that language is automatically activated while the HTML page is being displayed. Scripting languages tend to be reasonably easy to understand and, because they are simply text that is p

45、art of an HTML page, they load very quickly as part of the single server hit required to procure that page. The trade-off is that your code is exposed for everyone to see (and steal). Generally, however, you arent doing amazingly sophisticated things with scripting languages, so this is not too much

46、 of a hardship. This points out that the scripting languages used inside Web browsers are really intended to solve specific types of problems, primarily the creation of richer and more interactive graphical user interfaces (GUIs). However, a scripting language might solve 80 percent of the problems

47、encountered in client-side programming. Your problems might very well fit completely within that 80 percent, and since scripting languages can allow easier and faster development, you should probably consider a scripting language before looking at a more involved solution such as Java or ActiveX pro

48、gramming. The most commonly discussed browser scripting languages are JavaScript (which has nothing to do with Java; its named that way just to grab some of Javas marketing momentum), VBScript (which looks like Visual BASIC), and Tcl/Tk, which comes from the popular cross-platform GUI-building langu

49、age. There are others out there, and no doubt more in development. JavaScript is probably the most commonly supported. It comes built into both Netscape Navigator and the Microsoft Internet Explorer (IE). Unfortunately, the flavor of JavaScript on the two browsers can vary widely (the Mozilla browse

50、r, freely downloadable from www.M, supports the ECMAScript standard, which may one day become universally supported). In addition, there are probably more JavaScript books available than there are for the other browser languages, and some tools automatically create pages using JavaScript. However, i

51、f youre already fluent in Visual BASIC or Tcl/Tk, youll be more productive using those scripting languages rather than learning a new one. (Youll have your hands full dealing with the Web issues already.) JavaIf a scripting language can solve 80 percent of the client-side programming problems, what

52、about the other 20 percentthe “really hard stuff?” Java is a popular solution for this. Not only is it a powerful programming language built to be secure, cross-platform, and international, but Java is being continually extended to provide language features and libraries that elegantly handle proble

53、ms that are difficult in traditional programming languages, such as multithreading, database access, network programming, and distributed computing. Java allows client-side programming via the applet and with Java Web Start. An applet is a mini-program that will run only under a Web browser. The app

54、let is downloaded automatically as part of a Web page (just as, for example, a graphic is automatically downloaded). When the applet is activated, it executes a program. This is part of its beautyit provides you with a way to automatically distribute the client software from the server at the time t

55、he user needs the client software, and no sooner. The user gets the latest version of the client software without fail and without difficult reinstallation. Because of the way Java is designed, the programmer needs to create only a single program, and that program automatically works with all comput

56、ers that have browsers with built-in Java interpreters. (This safely includes the vast majority of machines.) Since Java is a full-fledged programming language, you can do as much work as possible on the client before and after making requests of the server. For example, you wont need to send a requ

57、est form across the Internet to discover that youve gotten a date or some other parameter wrong, and your client computer can quickly do the work of plotting data instead of waiting for the server to make a plot and ship a graphic image back to you. Not only do you get the immediate win of speed and

58、 responsiveness, but the general network traffic and load on servers can be reduced, preventing the entire Internet from slowing down. One advantage a Java applet has over a scripted program is that its in compiled form, so the source code isnt available to the client. On the other hand, a Java appl

59、et can be decompiled without too much trouble, but hiding your code is often not an important issue. Two other factors can be important. As you will see later in this book, a compiled Java applet can require extra time to download, if it is large. A scripted program will just be integrated into the

60、Web page as part of its text (and will generally be smaller and reduce server hits). This could be important to the responsiveness of your Web site. Another factor is the all-important learning curve. Regardless of what youve heard, Java is not a trivial language to learn. If youre a VISUAL BASIC pr