基于.NET的在線訂餐系統(tǒng)設(shè)計(jì)與開發(fā)

基于.NET的在線訂餐系統(tǒng)設(shè)計(jì)與開發(fā),基于,NET,在線,系統(tǒng),設(shè)計(jì),開發(fā) 編號(hào) 無錫太湖學(xué)院 畢業(yè)設(shè)計(jì)（論文） 相關(guān)資料 題目：基于.net的在線訂餐系統(tǒng)設(shè)計(jì)與開發(fā) 信機(jī) 系 計(jì)算機(jī)科學(xué)與技術(shù) 專業(yè) 學(xué) 號(hào)： 　　　0921125 　　　　 學(xué)生姓名： 包培培 指導(dǎo)教師： 　李朝鋒 （職稱：副教授） （職稱： ） 2013年05月25日 目 錄 一、畢業(yè)設(shè)計(jì)（論文）開題報(bào)告 二、畢業(yè)設(shè)計(jì)（論文）外文資料翻譯及原文 三、學(xué)生“畢業(yè)論文（論文）計(jì)劃、進(jìn)度、檢查及落實(shí)表” 四、實(shí)習(xí)鑒定表 無錫太湖學(xué)院 畢業(yè)設(shè)計(jì)（論文） 開題報(bào)告 題目：基于.net的在線訂餐系統(tǒng)設(shè)計(jì)與開發(fā) 信機(jī) 系 計(jì)算機(jī)科學(xué)與技術(shù) 專業(yè) 學(xué) 號(hào)： 0921125 學(xué)生姓名： 陸　 瑩 指導(dǎo)教師： 李朝鋒 （職稱：副教授 ） （職稱： ） 2012年12月06日 課題來源 自擬題目 科學(xué)依據(jù)（包括課題的科學(xué)意義；國內(nèi)外研究概況、水平和發(fā)展趨勢(shì)；應(yīng)用前景等） 隨著人們生活水平的提高，對(duì)飲食的要求也越來越高。餐飲業(yè)是一種個(gè)性化、多樣化的服務(wù)產(chǎn)業(yè)。通過網(wǎng)上訂餐,顧客不需到現(xiàn)場(chǎng),便可以為自己、家人、朋友聚會(huì)等購買美食。網(wǎng)上訂餐圖文并茂，更能及時(shí)更新信息和在線查看，有效地解決了餐過程中排隊(duì)，擁擠，餐單信息不能及時(shí)更新的問題。網(wǎng)上訂餐既節(jié)省時(shí)間，更為廣大客戶提供更多選擇。 據(jù)悉國外的許多知名餐飲企業(yè)在多年前就已經(jīng)開始了出現(xiàn)網(wǎng)上訂餐服務(wù)，并且受到了許多人士的歡迎。最近幾年這些企業(yè)的網(wǎng)上訂餐服務(wù)也在中國陸續(xù)推出、逐漸普及中?，F(xiàn)在我國多數(shù)餐廳使用的訂餐方式仍是電話訂餐，這種訂餐方式效率低，需人工記錄，容易遺漏和出錯(cuò)。當(dāng)然也有商家發(fā)現(xiàn)了新的市場(chǎng)開發(fā)網(wǎng)上業(yè)務(wù)。但是總體來說，我國的網(wǎng)上訂餐業(yè)務(wù)還處于形成期，有很大的成長空間。 人們通過網(wǎng)絡(luò)，可對(duì)菜品進(jìn)行預(yù)訂，這樣不僅能夠節(jié)約了時(shí)間，也能提高餐飲企業(yè)的訂餐管理效率。最重要的是，這樣的訂餐方式不易出錯(cuò)，對(duì)每位客戶的訂餐處理及時(shí)，實(shí)現(xiàn)了高度智能化管理。因此網(wǎng)上訂餐有望發(fā)展成一種潮流的訂餐方式，成為餐飲業(yè)銷售增長的新模式。 研究內(nèi)容 本系統(tǒng)將實(shí)現(xiàn)在線網(wǎng)上訂餐業(yè)務(wù)的自動(dòng)化管理。整個(gè)系統(tǒng)由以下幾個(gè)基本模塊組成。 商品管理：主要實(shí)現(xiàn)對(duì)商品實(shí)時(shí)查詢，及時(shí)增加、修改、刪除相關(guān)信息的能。訂單管理：用戶可以查看已經(jīng)預(yù)定的商品，預(yù)訂的時(shí)間，付款情況。用戶管理：新客戶可申請(qǐng)賬號(hào)進(jìn)行菜品的預(yù)訂，已經(jīng)申請(qǐng)的用戶可根據(jù)申請(qǐng)的賬號(hào)登陸系統(tǒng)。商家可以對(duì)錄入的會(huì)員信息進(jìn)行管理。 系統(tǒng)管理：系統(tǒng)管理人員可對(duì)對(duì)軟件的維護(hù)和權(quán)限進(jìn)行管理。包括系統(tǒng)維護(hù)向?qū)В瑱?quán)限管理。 數(shù)據(jù)庫的需求： 因?yàn)闊o法連接到大型數(shù)據(jù)庫，只能在本機(jī)上安裝SQL Server 2000數(shù)據(jù)庫軟件。在此數(shù)據(jù)庫中建立需要的表來保存數(shù)據(jù)。 擬采取的研究方法、技術(shù)路線、實(shí)驗(yàn)方案及可行性分析 在Windows系統(tǒng)下基于.NET環(huán)境使用Microsoft Visual Studio 2005開發(fā)軟件進(jìn)行系統(tǒng)開發(fā)，并采用SQL Server 2000作為數(shù)據(jù)庫服務(wù)器進(jìn)行數(shù)據(jù)處理。 首先熟悉所運(yùn)用到的開發(fā)軟件，收集整理相關(guān)的資料信息。然后了解整個(gè)訂餐系統(tǒng)流程，設(shè)計(jì)系統(tǒng)總體框架，完成主體模塊功能；對(duì)系統(tǒng)進(jìn)行排版，界面的美化；實(shí)現(xiàn)系統(tǒng)與數(shù)據(jù)庫的連接。最終對(duì)系統(tǒng)進(jìn)行測(cè)試，查找漏洞，并逐步完善系統(tǒng)。 網(wǎng)上訂餐可以方便人們的生活、提高效率。使人們可以足不出戶就可完成訂餐，網(wǎng)上訂餐系統(tǒng)不僅可以實(shí)現(xiàn)客戶在線訂餐的功能，黑可以在此基礎(chǔ)上完善配套的服務(wù)。讓人們?cè)谏钪邢硎艿娇萍歼M(jìn)步所帶來的便利。如今經(jīng)濟(jì)的發(fā)展推動(dòng)了互聯(lián)網(wǎng)技術(shù)的飛速發(fā)展，在訂餐系統(tǒng)也顯示這越來越強(qiáng)大的優(yōu)勢(shì)。 研究計(jì)劃及預(yù)期成果 研究計(jì)劃： 2012年12月12日以前： 收集相關(guān)資料，撰寫《開題報(bào)告》，并按開題報(bào)告條款進(jìn)入畢業(yè)設(shè)計(jì)階段。 2012年12月~2013年1月：初步完成畢業(yè)設(shè)計(jì)系統(tǒng)框架.。 2013年2月：完成各功能模塊編碼 。 2013年3月~2013年4月：測(cè)試、驗(yàn)收，完善，撰寫畢業(yè)論文。 2013年5月： 上交論文、系統(tǒng)代碼、根據(jù)導(dǎo)師意見修改畢業(yè)論文并完善論文。 2013年6月2日~4日：進(jìn)行畢業(yè)答辯。 預(yù)期成果：根據(jù)計(jì)劃及時(shí)的完成每階段的任務(wù)。 特色或創(chuàng)新之處 本課題是基于.NET架構(gòu)下的ASP.NET和SQL Server 2000技術(shù)聯(lián)合開發(fā)完成。 訂餐信息簡潔明了，配有圖片文字說明，信息一目了然。 宣傳效果明顯，面向客戶群體廣泛。 無需安裝第三方軟件，甚至能過通過手機(jī)上網(wǎng)訂餐。 操作簡變，訂餐信息準(zhǔn)確，更能及時(shí)反應(yīng)最新的菜品情況。 可實(shí)現(xiàn)預(yù)定功能，節(jié)省時(shí)間。 已具備的條件和尚需解決的問題 已具備的條件： 1、 一臺(tái)計(jì)算機(jī)。 2、 客戶的基本需求，訂餐的總體流程。 3、 Microsoft Visual Studio 2005和SQL Server 2000軟件。 尚需解決的問題： 1、 詳細(xì)的需求分析 2、 具體模塊功能的實(shí)現(xiàn) 指導(dǎo)教師意見 此處日期2011年11月14日-2010年11月18日之間 指導(dǎo)教師簽名： 年 月 日 教研室（學(xué)科組、研究所）意見 教研室主任簽名： 年 月 日 系意見 主管領(lǐng)導(dǎo)簽名： 年 月 日 ASP.NET Technique 1. Building ASP.NET Pages ASP.NET and the .NET Framework ASP.NET is part of Microsoft's overall .NET framework，which contains a vast set of programming classes designed to satisfy any conceivable programming need. In the following two sections，you learn how ASP.NET fits within the .NET framework，and you learn about the languages you can use in your ASP.NET pages. The .NET Framework Class Library agine that you are Microsoft. Imagine that you have to support multiple programming languages—such as Visual Basic，JScript，and C++. A great deal of the functionality of these programming languages overlaps. For example，for each language，you would have to include methods for accessing the file system，working with databases，and manipulating strings. Furthermore，these languages contain similar programming constructs. Every language，for example，can represent loops and conditionals. Even though the syntax of a conditional written in Visual Basic differs from the syntax of a conditional written in C++，the programming function is the same. Finally，most programming languages have similar variable data types. In most languages，you have some means of representing strings and integers，for example. The maximum and minimum size of an integer might depend on the language，but the basic data type is the same. Maintaining all this functionality for multiple languages requires a lot of work. Why keep reinventing the wheel? Wouldn't it be easier to create all this functionality once and use it for every language? The .NET Framework Class Library does exactly that. It consists of a vast set of classes designed to satisfy any conceivable programming need. For example，the .NET framework contains classes for handling database access，working with the file system，manipulating text，and generating graphics. In addition，it contains more specialized classes for performing tasks such as working with regular expressions and handling network protocols. The .NET framework，furthermore，contains classes that represent all the basic variable data types such as strings，integers，bytes，characters，and arrays. Most importantly，for purposes of this book，the .NET Framework Class Library contains classes for building ASP.NET pages. You need to understand，however，that you can access any of the .NET framework classes when you are building your ASP.NET pages. Understanding Namespaces As you might guess，the .NET framework is huge. It contains thousands of classes (over 3，400). Fortunately，the classes are not simply jumbled together. The classes of the .NET framework are organized into a hierarchy of namespaces. ASP Classic Note In previous versions of Active Server Pages，you had access to only five standard classes (the Response，Request，Session，Application，and Server objects). ASP.NET，in contrast，provides you with access to over 3，400 classes! A namespace is a logical grouping of classes. For example，all the classes that relate to working with the file system are gathered together into the System.IO namespace. The namespaces are organized into a hierarchy (a logical tree). At the root of the tree is the System namespace. This namespace contains all the classes for the base data types，such as strings and arrays. It also contains classes for working with random numbers and dates and times. You can uniquely identify any class in the .NET framework by using the full namespace of the class. For example，to uniquely refer to the class that represents a file system file (the File class)，you would use the following: System.IO.File System.IO refers to the namespace，and File refers to the particular class. NOTE You can view all the namespaces of the standard classes in the .NET Framework Class Library by viewing the Reference Documentation for the .NET Framework. Standard ASP.NET Namespaces The classes contained in a select number of namespaces are available in your ASP.NET pages by default. (You must explicitly import other namespaces.) These default namespaces contain classes that you use most often in your ASP.NET applications: System— Contains all the base data types and other useful classes such as those related to generating random numbers and working with dates and times. System.Collections— Contains classes for working with standard collection types such as hash tables，and array lists. System.Collections.Specialized— Contains classes that represent specialized collections such as linked lists and string collections. System.Configuration— Contains classes for working with configuration files (Web.config files). System.Text— Contains classes for encoding，decoding，and manipulating the contents of strings. System.Text.RegularExpressions— Contains classes for performing regular expression match and replace operations. System.Web— Contains the basic classes for working with the World Wide Web，including classes for representing browser requests and server responses. System.Web.Caching— Contains classes used for caching the content of pages and classes for performing custom caching operations. System.Web.Security— Contains classes for implementing authentication and authorization such as Forms and Passport authentication. System.Web.SessionState— Contains classes for implementing session state. System.Web.UI— Contains the basic classes used in building the user interface of ASP.NET pages. System.Web.UI.HTMLControls— Contains the classes for the HTML controls. System.Web.UI.WebControls— Contains the classes for the Web controls. .NET Framework -Compatible Languages For purposes of this book，you will write the application logic for your ASP.NET pages using Visual Basic as your programming language. It is the default language for ASP.NET pages. Although you stick to Visual Basic in this book，you also need to understand that you can create ASP.NET pages by using any language that supports the .NET Common Language Runtime. Out of the box，this includes C#，JScript.NET，and the Managed Extensions to C++. NOTE Dozens of other languages created by companies other than Microsoft have been developed to work with the .NET framework. Some examples of these other languages include Python，SmallTalk，Eiffel，and COBOL. This means that you could，if you really wanted to，write ASP.NET pages using COBOL. Regardless of the language that you use to develop your ASP.NET pages，you need to understand that ASP.NET pages are compiled before they are executed. This means that ASP.NET pages can execute very quickly. The first time you request an ASP.NET page，the page is compiled into a .NET class，and the resulting class file is saved beneath a special directory on your server named Temporary ASP.NET Files. For each and every ASP.NET page，a corresponding class file appears in the Temporary ASP.NET Files directory. Whenever you request the same ASP.NET page in the future，the corresponding class file is executed. When an ASP.NET page is compiled，it is not compiled directly into machine code. Instead，it is compiled into an intermediate-level language called Microsoft Intermediate Language (MSIL). All .NET-compatible languages are compiled into this intermediate language. An ASP.NET page isn't compiled into native machine code until it is actually requested by a browser. At that point，the class file contained in the Temporary ASP.NET Files directory is compiled with the .NET framework Just in Time (JIT) compiler and executed. The magical aspect of this whole process is that it happens automatically in the background. All you have to do is create a text file with the source code for your ASP.NET page，and the .NET framework handles all the hard work of converting it into compiled code for you. ASP CLASSIC NOTE What about VBScript? Before ASP.NET，VBScript was the most popular language for developing Active Server Pages. ASP.NET does not support VBScript，and this is good news. Visual Basic is a superset of VBScript，which means that Visual Basic has all the functionality of VBScript and more. So，you have a richer set of functions and statements with Visual Basic. Furthermore，unlike VBScript，Visual Basic is a compiled language. This means that if you use Visual Basic to rewrite the same code that you wrote with VBScript，you can get better performance. If you have worked only with VBScript and not Visual Basic in the past，don't worry. Since VBScript is so closely related to Visual Basic，you'll find it easy to make the transition between the two languages. NOTE Microsoft includes an interesting tool named the IL Disassembler (ILDASM) with the .NET framework. You can use this tool to view the disassembled code for any of the ASP.NET classes in the Temporary ASP.NET Files directory. It lists all the methods and properties of the class and enables you to view the intermediate-level code. This tool also works with all the ASP.NET controls discussed in this chapter. For example，you can use the IL Disassembler to view the intermediate-level code for the TextBox control (located in a file named System.Web.dll). Introducing ASP.NET Controls ASP.NET controls provide the dynamic and interactive portions of the user interface for your Web application. The controls render the content that the users of your Web site actually see and interact with. For example，you can use controls to create HTML form elements，interactive calendars，and rotating banner advertisements. ASP.NET controls coexist peacefully with HTML content. Typically，you create the static areas of your Web pages with normal HTML content and create the dynamic or interactive portions with ASP.NET controls. The best way to understand how ASP.NET controls work in an HTML page is to look at a simple Web Forms Page. Adding Application Logic to an ASP.NET Page The second building block of an ASP.NET page is the application logic，which is the actual programming code in the page. You add application logic to a page to handle both control and page events. If a user clicks a Button control within an HTML form，for example，the Button control raises an event (the Click event). Typically，you want to add code to the page that does something in response to this event. For example，when someone clicks the Button control，you might want to save the form data to a file or database. Controls are not the only things that can raise events. An ASP.NET page itself raises several events every time it is requested. For example，whenever you request a page，the page's Load event is triggered. You can add application logic to the page that executes whenever the Load event occurs. 2. Building Forms with Web Server Controls Building Smart Forms You use several of the basic Web controls to represent standard HTML form elements such as radio buttons，text boxes，and list boxes. You can use these controls in your ASP.NET pages to create the user interface for your Web application. The following sections provide detailed overviews and programming samples for each of these Web controls. Controlling Page Navigation In the following sections，you learn how to control how a user moves from one ASP.NET page to another. First，you learn how to submit an HTML form to another page and retrieve form information. Next，you learn how to use the Redirect() method to automatically transfer a user to a new page. Finally，you learn how to link pages together with the HyperLink control. Applying Formatting to Controls In the following sections，you learn how to make more attractive Web forms. First，you look at an overview of the formatting properties common to all Web controls; they are the formatting properties of the base control class. Next，you learn how to apply Cascading Style Sheet styles and classes to Web controls. 3. Performing Form Validation with Validation Controls Using Client-side Validation Traditionally，Web developers have faced a tough choice when adding form validation logic to their pages. You can add form validation routines to your server-side code，or you can add the validation routines to your client-side code. The advantage of writing validation logic in client-side code is that you can provide instant feedback to your users. For example，if a user neglects to enter a value in a required form field，you can instantly display an error message without requiring a roundtrip back to the server. People really like client-side validation. It looks great and creates a better overall user experience. The problem，however，is that it does not work with all browsers. Not all browsers support JavaScript，and different versions of browsers support different versions of JavaScript，so client-side validation is never guaranteed to work. For this reason，in the past，many developers decided to add all their form validation logic exclusively to server-side code. Because server-side code functions correctly with any browser，this course of action was safer. Fortunately，the Validation controls discussed in this chapter do not force you to make this difficult choice. The Validation controls automatically generate both client-side and server-side code. If a browser is capable of supporting JavaScript，client-side validation scripts are automatically sent to the browser. If a browser is incapable of supporting JavaScript，the validation routines are automatically implemented in server-side code. You should be warned，however，that client-side validation works only with Microsoft Internet Explorer version 4.0 and higher. In particular，the client-side scripts discussed in this chapter do not work with any version of Netscape Navigator. Requiring Fields:The RequiredFieldValidator Control You use RequiredFieldValidator in a Web form to check whether a control has a value. Typically，you use this control with a TextBox control. However，nothing is wrong with using RequiredFieldValidator with other input controls such as RadioButtonList. Validating Expression:The RegularExpressionValidator Control You can use RegularExpressionValidator to match the value entered into a form field to a regular expression. You can use this control to check whether a user has entered，for example，a valid e-mail address，telephone number，or username or password. Samples of how to use a regular expression to perform all these validation tasks are provided in the following sections. Comparing Values:The CompareValidator Control The CompareValidator control performs comparisons between the data entered into a form field and another value. The other value can be a fixed value，such as a particular number，or a value entered into another control. Summarizing Errors:The ValidationSummary Control Imagine that you have a form with 50 form fields. If you use only the Validation controls discussed in the previous sections of this chapter to display errors，seeing an error message on the page might be difficult. For example，you might have to scroll down to the 48th form field to find the error message. Fortunately，Microsoft includes a ValidationSummary control with the Validation controls. You can use this control to summarize all the errors at the top of a page，or wherever else you want. 4. Advanced Control Programming Working with View State By default，almost all ASP.NET controls retain the values of their properties between form posts. For example，if you assign text to a Label control and submit the form，when the page is rendered again，the contents of the Label control are preserved. The magic of view state is that it does not depend on any special server or browser properties. In particular，it does not depend on cookies，session variables，or application variables. View state is implemented with a hidden form field called VIEWSTATE that is automatically created in every Web Forms Page. When used wisely，view state can have a dramatic and positive effect on the performance of your Web site. For example，if you display database data in a control that has view state enabled，you do not have to return to the database each time the page is posted back to the server. You can automatically preserve the data within the page's view state between form posts. Displaying and Hiding Content Imagine that you are creating a form with an optional section. For example，imagine that you are creating an online tax form，and you want to display or hide a section that contains questions that apply only to married tax filers. Or，imagine that you want to add an additional help button to the tax form. You might want to hide or display detailed instructions for completing form questions depending on a user's preferences. Finally，imagine that you want to break the tax form into multiple pages so that a person views only one part of the tax form at a time. In the following sections，you learn about the properties that you can use to hide and display controls in a form. You learn how to use the Visible and Enabled properties with individual controls and groups of controls to hide and display page content. Using