票務(wù)易購(gòu)系統(tǒng)之火車票板塊畢業(yè)設(shè)計(jì)(論文)_第1頁(yè)
票務(wù)易購(gòu)系統(tǒng)之火車票板塊畢業(yè)設(shè)計(jì)(論文)_第2頁(yè)
票務(wù)易購(gòu)系統(tǒng)之火車票板塊畢業(yè)設(shè)計(jì)(論文)_第3頁(yè)
票務(wù)易購(gòu)系統(tǒng)之火車票板塊畢業(yè)設(shè)計(jì)(論文)_第4頁(yè)
票務(wù)易購(gòu)系統(tǒng)之火車票板塊畢業(yè)設(shè)計(jì)(論文)_第5頁(yè)
已閱讀5頁(yè),還剩69頁(yè)未讀, 繼續(xù)免費(fèi)閱讀

下載本文檔

版權(quán)說(shuō)明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請(qǐng)進(jìn)行舉報(bào)或認(rèn)領(lǐng)

文檔簡(jiǎn)介

1、大連交通大學(xué)信息工程學(xué)院2012屆本科生畢業(yè)設(shè)計(jì)(論文)外文翻譯大連交通大學(xué)信息工程學(xué)院畢業(yè)設(shè)計(jì)(論文)任務(wù)書(shū)題 目票務(wù)易購(gòu)系統(tǒng)之火車票板塊任務(wù)及要求:1.設(shè)計(jì)(研究)內(nèi)容和要求任務(wù):1、 調(diào)查票務(wù)系統(tǒng)當(dāng)前技術(shù)的發(fā)展近況,完成實(shí)習(xí)報(bào)告,字?jǐn)?shù)不少于3000,第三周交給指導(dǎo)老師。2、 結(jié)合自己實(shí)習(xí)情況安排進(jìn)度,填寫(xiě)進(jìn)度計(jì)劃表,第二周完成后交給指導(dǎo)老師簽字,并嚴(yán)格執(zhí)行。3、 按照軟件工程思想,獨(dú)立完成系統(tǒng)的設(shè)計(jì)和程序開(kāi)發(fā),完成代碼估計(jì)2000行左右。4、 用jsp技術(shù)實(shí)現(xiàn)票務(wù)系統(tǒng)基本功能。5、 程序簡(jiǎn)潔,算法可行,運(yùn)行情況良好。要求:1、 每周和指導(dǎo)老師至少見(jiàn)面溝通一次,回報(bào)課題進(jìn)展情況,接受老師詢

2、問(wèn)。2、 接到任務(wù)書(shū)后,查閱與題目及專業(yè)相關(guān)的外文資料進(jìn)行翻譯,要求不少于10000個(gè)外文字符,譯出漢字不得少于3000,于第四周交給指導(dǎo)老師審閱。3、 畢業(yè)設(shè)計(jì)第13周完成畢業(yè)論文的裝訂,并由指導(dǎo)老師評(píng)閱。論文要求12000字以上,包括綜述、系統(tǒng)總體設(shè)計(jì)、系統(tǒng)實(shí)現(xiàn)、性能分析、結(jié)論等。4、 教學(xué)第13周通過(guò)中軟及教研室組織進(jìn)行軟件驗(yàn)收,驗(yàn)收時(shí)要提供軟件使用說(shuō)明書(shū)。5、 于第13周提出畢業(yè)答辯申請(qǐng)并簽字。6、 第14 周答辯,要求制作ppt2.原始依據(jù)通過(guò)大學(xué)幾年的學(xué)習(xí),已經(jīng)學(xué)習(xí)了諸如軟件工程、數(shù)據(jù)庫(kù)原理及應(yīng)用、數(shù)據(jù)結(jié)構(gòu)、c+、visual basic、java等多門(mén)程序設(shè)計(jì)語(yǔ)言和網(wǎng)絡(luò)等基礎(chǔ)知識(shí)

3、和專業(yè)知識(shí),學(xué)生有能力而且可以獨(dú)立完成小中型項(xiàng)目的設(shè)計(jì)與開(kāi)發(fā)。學(xué)?,F(xiàn)有設(shè)備和環(huán)境可以提供給學(xué)生實(shí)習(xí)和上機(jī),而且具有專業(yè)老師可以指導(dǎo)學(xué)生。3.參考文獻(xiàn)1 孫鑫.servlet/jsp深入詳解-基于tomcat的web開(kāi)發(fā).電子工業(yè)出版社.2008-8-12 bergsten,horeilly javaamerican:sernni yey3 張孝祥,徐明華jsp基礎(chǔ)與案例開(kāi)發(fā)詳解清華大學(xué)出版社2009-8-14 李丹丹sql server 2000數(shù)據(jù)庫(kù)實(shí)訓(xùn)教程清華大學(xué)出版社2007-8-15 王毅sql應(yīng)用開(kāi)發(fā)范例寶典:軟件工程師典藏人民郵電出版社2008-7-16 楊林軟件工程實(shí)踐教程(第2

4、版)電子工業(yè)出版社2011-4-17 朱少民軟件測(cè)試方法和技術(shù)(第二版)清華大學(xué)出版社2010-7-18 伊樂(lè)斯架構(gòu)實(shí)戰(zhàn)軟件架構(gòu)設(shè)計(jì)的過(guò)程機(jī)械工業(yè)出版社2010-4-19 paaton,r軟件測(cè)試(英文版第二版)機(jī)械工業(yè)出版社2006-1-110 多布斯軟件測(cè)試與持續(xù)質(zhì)量改進(jìn)人民郵電出版社2011-7-111 張華祥,劉弘.java語(yǔ)言基礎(chǔ)教程m.北京:清華大學(xué)出版社,200712 耿祥義,張躍平.java課程設(shè)計(jì)m.北京:清華大學(xué)出版社,200813 耿祥義,張躍平.jsp使用教程m.北京:清華大學(xué)出版社,2007指導(dǎo)教師簽字:教研室主任簽字: 年 月 日大連交通大學(xué)信息工程學(xué)院畢業(yè)設(shè)計(jì)(論

5、文)進(jìn)度計(jì)劃與考核表學(xué)生姓名付婷婷專業(yè)班級(jí)軟件工程08-3班指導(dǎo)教師閻樹(shù)昕 劉瑞杰本課題其他人員無(wú)題目票務(wù)易購(gòu)系統(tǒng)之火車票板塊日期計(jì)劃完成內(nèi)容完成情況指導(dǎo)老師檢查簽字第1周實(shí)習(xí)調(diào)研,查閱課題相關(guān)外文資料第2周了解行業(yè)狀況、查閱文獻(xiàn)資料,閱讀資料,撰寫(xiě)調(diào)研報(bào)告第3周完成后臺(tái)數(shù)據(jù)庫(kù)的設(shè)計(jì)并編碼,完成部分論文第4周進(jìn)行需求分析第5周進(jìn)行概要設(shè)計(jì)第6周進(jìn)行概要設(shè)計(jì), 基本框架完成,提交畢業(yè)論文提綱第7周完成后臺(tái)數(shù)據(jù)庫(kù)的設(shè)計(jì)并編碼,完成部分論文第8周完成后臺(tái)數(shù)據(jù)庫(kù)的設(shè)計(jì)并編碼,完成部分論文第9周繼續(xù)編碼并進(jìn)行測(cè)試,繼續(xù)編寫(xiě)畢業(yè)設(shè)計(jì)論文第10周繼續(xù)進(jìn)行程序測(cè)試,繼續(xù)編寫(xiě)畢業(yè)設(shè)計(jì)論文第11周整理資料、文檔、

6、圖表等,修改畢業(yè)設(shè)計(jì)論文第12周完成畢業(yè)設(shè)計(jì)論文,打印,按要求裝訂第13周軟件驗(yàn)收和準(zhǔn)備畢業(yè)設(shè)計(jì)答辯第14周畢業(yè)設(shè)計(jì)答辯及成績(jī)?cè)u(píng)定指導(dǎo)教師簽字: 年月日注:“計(jì)劃完成內(nèi)容”由學(xué)生本人認(rèn)真填寫(xiě),其它由指導(dǎo)教師考核時(shí)填寫(xiě)。大連交通大學(xué)信息工程學(xué)院畢業(yè)設(shè)計(jì)(論文)外文翻譯學(xué)生姓名 付婷婷 專業(yè)班級(jí) 軟件工程08-3班指導(dǎo)教師 閻樹(shù)昕劉瑞杰 職 稱 高工講師 所在單位 信息科學(xué)系軟件工程教研室 教研室主任 劉瑞杰 完成日期 2012年4月13日how to troubleshoot connectivity issues in sql server 2000this article can help

7、you to resolve connectivity problems with microsoft sql server 2000. this article contains descriptions of common connectivity problems and the steps that you can take to help resolve your connectivity problems. sql server 2000 supports several methods of communication between the instance of sql se

8、rver and the client applications. if your client application and the instance of sql server reside on the same computer, microsoft windows interprocess communication (ipc) components, such as local named pipes or the shared memory protocol, are used to communicate. however, when the client applicati

9、on and the instance of sql server reside on different computers, a network ipc, such as tcp/ip or named pipes, is used to communicate.sql server 2000 uses net-library, a dll, to communicate with a particular network protocol. a matching pair of net-libraries must be active on the client computer and

10、 the server computer to support the network protocol that you want to use. for example, if you want to enable a client application to communicate with a specific instance of sql server across tcp/ip, the client tcp/ip sockets net-library (dbnetlib.dll) must be configured to connect to the server on

11、the client computer. likewise, the server tcp/ip sockets net-library (ssnetlib.dll) must listen on the server computer. in this scenario, the tcp/ip protocol stack must be installed on both the client computer and the server computer.after you install sql server 2000, you can configure the propertie

12、s of the client net-libraries by using client network utility. you can configure the properties of the server net-libraries by using server network utility (svrnetcn.exe). the server net-libraries are installed during the installation of the server tools in sql server setup. however, some of the ser

13、ver net-libraries may not be active. by default, sql server 2000 enables and listens on tcp/ip, named pipes, and shared memory. therefore, for a client to connect to a server computer, the client must connect by using a client net-library that matches one of the server net-libraries that is currentl

14、y being used by the instance of sql server.for additional information about sql server communication components and net-libraries, see the following topics in sql server books online: communication componentsclient and server net-librariesmanaging clientsmost of the connectivity issues that you may

15、notice in sql server 2000 occur because of problems with tcp/ip, windows authentication, or a combination of tcp/ip and windows authentication. important before you start to troubleshoot connectivity issues in sql server 2000, make sure that the mssqlserver service is started on the computer that is

16、 running sql server.verify your dns settingsthe name resolution process in domain name system (dns) is used to resolve the ip address to the name of the instance of sql server. if the name resolution process does not work correctly, the instance of sql server is not reachable, and you may receive on

17、e or more of the following error messages: sql server does not exist or access deniedgeneral network errorcannot generate sspi contextto verify that the name resolution process is resolving the correct server, you can ping the server by using the server name and the ip address of the server. to do s

18、o, follow these steps: 1.click start, and then click run.2.in the run dialog box, type cmd in the open box, and then click ok.3.at the command prompt, run the following command:ping note the ip address that is returned.4.at the command prompt, run the following command (where ip address is the ip ad

19、dress that you noted in step 3)ping a verify that the command resolves to the correct server name. if either of the specified commands are not successful, time out, or do not return the correct values, the dns lookup is not working correctly or the problem occurs because of other networking or routi

20、ng issues. to see your current dns settings, run the following command at a command prompt:to %systemroot%system32driversetchosts file on the client computer. you can also work around the problem by connecting to the server by using the named pipes net-library.verify the enabled protocols and aliase

21、sconnectivity problems may occur if the alias on the client computer is set incorrectly. you can view the aliases by using client network utility. to do so, follow these steps: 1.start client network utility. if the sql server client tools are installed on the computer that is running the client app

22、lication, follow these steps to start client network utility: a. click start, and then point to programs.b. point to microsoft sql server, and then click client network utility.if the sql server client tools are not installed on the client computer, follow these steps to start client network utility

23、: a. click start, and then click run.b. in the run dialog box, type cliconfg in the open box, and then click ok.2.in the sql server client network utility window, click the general tab, and then enable all the protocols that you want to use.note you must at least enable the tcp/ip protocol and the n

24、amed pipes protocol.3.click the alias tab, and then verify the aliases that are configured for the instance of sql server. 4.verify the properties of the aliases to make sure that the server name or ip address and the protocol are configured correctly.you can create a new alias to test the connectiv

25、ity by using the server name, the ip address, or even by using a different protocol.note earlier versions of microsoft data access components (mdac) have a different user interface for client network utility. therefore, if you do not see the options that are listed in this article, install a later v

26、ersion of mdac on the computer that is running the client application.verify that the instance of sql server is listening correctlyto verify that the instance of sql server is listening on named pipes, tcp/ip, or another protocol that you are using at the client application, open the current sql ser

27、ver error log file. the sql server error log file may contain entries that are similar to the following:2003-11-06 09:49:36.17 server sql server listening on tcp, shared memory, named pipes. 2003-11-06 09:49:36.17 server sql server listening on :1433, :1433.if you analyze the ent

28、ries in the sql server error log file, you can verify that the instance of sql server is listening on the correct ip address and on the correct port. by default, a default instance of sql server listens on the port 1433. you can also use server network utility to verify the protocol settings for sql

29、 server and to change the properties in sql server, including the protocols that can connect to sql server and the ports that can be used. for more information about using server network utility, see the sql server network utility topic in sql server books online. sometimes, sql server 2000 may not

30、bind to port 1433 or any other specified port. this problem may occur if the port is being used by another application or if you are trying to connect by using an ip address that is not correct. therefore, the tcp/ip connections to sql server may not be successful and you may receive the following e

31、rror message in the sql server error log file: 2001-11-14 15:49:14.12 server supersocket info: bind failed on tcp if you cannot connect to the instance of sql server by using a tcp/ip connection, try to use the named pipes protocol or the shared memory protocol. run the following command at a comman

32、d prompt to obtain information about the ports that are in use:you can also use the portqry command-line utility to obtain more information about the ports that are in use.note for named instances of sql server, sql server dynamically determines the port and listens on the determined port. therefore

33、, when you start the named instance of sql server, sql server tries to listen on the port that was previously being used. if sql server cannot bind to that port, the named instance may dynamically bind to a different port. in that situation, make sure that the client application is also set to deter

34、mine the port dynamically. alternatively, you can also specify a static port for the named instance to bind to and to listen on by using client network utility.connectivity problems may also occur because of problems with mdac. for example, a software installation may overwrite some of the mdac file

35、s or change the permissions that you must have to access the mdac files. you can run the mdac component checker to verify the mdac installation on your computer.note if you are connecting to a named instance of sql server, make sure that you are running mdac 2.6 or later on your computer. earlier ve

36、rsions of mdac do not recognize named instances of sql server. therefore, connections to named instances may not be successful.you can use the odbcping.exe utility to verify connections through the sql server odbc driver.you can also test connectivity to the instance of sql server by using a .udl fi

37、le.troubleshoot firewall issuesif firewall exists between the client computer and the computer that is running sql server, make sure that the ports that are required to communicate through the firewall are open.if you use the tcp/ip protocol to connect to the instance of sql server, make sure that y

38、ou can use the telnet program to connect to the port where sql server is listening. to use the telnet program, run the following command at a command prompt: telnet if the telnet program is not successful and you receive an error message, resolve the error and then try to connect again.note because

39、of issues that were caused by the slammer virus, the user datagram protocol (udp) port 1434 may be blocked on your firewall.troubleshoot authentication and security issuesconnections to sql server may not be successful because of authentication failures. if the authentication fails, you may receive

40、one of the following error messages:login failed for user login failed for user ntauthorityanonymous logonlogin failed for user nullif you receive an error message because of an authentication failure and the error message does not mention a specific sql server login name, troubleshoot the problem w

41、ith windows authentication. you may receive the following error message because of problems with windows authentication: cannot generate sspi contextthe following problems may cause authentication and security issues: problems occur with ntlm authentication or with kerberos authentication.the domain

42、 controller cannot be contacted because of connectivity issues.problems occur with trust relationships across domains.for more information about possible causes, see the event logs on the computer. to work around connectivity problems with windows authentication, you can use sql server authenticatio

43、n to connect to the instance of sql server. if the connection is not successful when you use sql server authentication, you receive the following error message: login failed for user . not associated with a trusted connectionto troubleshoot this problem, follow these steps. warning if you use regist

44、ry editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. microsoft cannot guarantee that you can solve problems that result from using registry editor incorrectly. use registry editor at your own risk. 1.make sure that the instance of sql server

45、is configured to use windows authentication and sql server authentication. to do so, make sure that the following registry keys are on the computer that is running sql server. for the d server:hkey_local_machinesoftwaremicrosoftmssqlservermssqlserverloginmodefor the named instance of sql server: hke

46、y_local_machinesoftwaremicrosoftmicrosoftsqlservermssqlserverloginmodemake sure that the following registry key values are set:authentication typevaluewindows authentication only1mixed mode (sql server authentication and windows authentication)2note if you make any changes to the registry, you must

47、stop and then restart the instance of sql server for the changes to take effect.2.try to connect to the instance of sql server by using different windows accounts or sql server login accounts. this can help determine if the connection is not successful because of problems with a particular login acc

48、ount. for example, the password of the login account may have been changed.3.try to connect to the instance of sql server by using different protocols. for example, the connections that use the tcp/ip protocol with windows authentication may not be successful, but connections that use the named pipe

49、s protocol with windows authentication may be successful.if you are using certificates, you may receive a secure sockets layer (ssl) security error message when you try to connect to the instance of sql server. troubleshoot stress on tcp/ip socketswhen you use the sql server odbc driver, the microso

50、ft ole db provider for sql server, or the system.data.sqlclient managed provider, you can disable connection pooling by using the appropriate application programming interfaces (apis). when you disable connection pooling and your application frequently opens and closes connections, the stress on the

51、 underlying sql server network library may increase. sometimes, the web servers and the jdbc drivers may also try to connect to the instance of sql server. therefore, the increase in connection requests to sql server may be more than sql server can handle. this may stress the tcp/ip sockets, and you

52、 may receive the following error message in the sql server error log file: 2003-08-07 20:46:21.11 server error: 17832, severity: 20, state: 6 2003-08-07 20:46:21.11 server connection opened but invalid login packet(s) sent. connection closed.for additional information, click the following article nu

53、mbers to view the articles in the microsoft knowledge base: 154628 ( inf: sql logs 17832 with multiple tcpip connection requests 328476 ( tcp/ip settings for sql server drivers when pooling is disabled note you may not notice the stress on tcp/ip sockets if you are running sql server 2000 sp3 or sql

54、 server 2000 sp3a because a limit on the number of login packets was added. the 17832 error occurs when you use third-party drivers to connect to the instance of sql server. to resolve this problem, contact the third-party vendor and obtain drivers that have been tested to work with sql server 2000

55、sp3 and sql server 2000 sp3a.see if the instance of sql server is started in single-user modeif the instance of sql server that you are trying to connect to is started in single-user mode, only one connection can be established with sql server. if you have software running on your computer that auto

56、matically connects to sql server, the software can easily use the only connection. for example, the following software can automatically connect to the instance of sql server:sql server agentthird-party backup softwarethird-party monitoring softwarethird-party virus softwaremicrosoft internet inform

57、ation services (iis)sql server enterprise manager the client application that is trying to connect to the instance of sql server receives the following error message: sql server does not exist or access deniedthis error generally occurs during sql cluster setup and service pack setup when the setup process starts the instance of sql server in single-user mode. the specified applications may automatically connect t

溫馨提示

  • 1. 本站所有資源如無(wú)特殊說(shuō)明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請(qǐng)下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請(qǐng)聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁(yè)內(nèi)容里面會(huì)有圖紙預(yù)覽,若沒(méi)有圖紙預(yù)覽就沒(méi)有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 人人文庫(kù)網(wǎng)僅提供信息存儲(chǔ)空間,僅對(duì)用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對(duì)用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對(duì)任何下載內(nèi)容負(fù)責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請(qǐng)與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時(shí)也不承擔(dān)用戶因使用這些下載資源對(duì)自己和他人造成任何形式的傷害或損失。

最新文檔

評(píng)論

0/150

提交評(píng)論