畢業(yè)論文-基于SQL Server的酒店管理信息系統(tǒng)

摘要關(guān)鍵字AbstractSummaryofhotelservicesinmateriallifeabundant,therapiddevelopmentofserviceindustrytodaymoreandmoreandpeople'slives.Thisrequiresacomprehensivemanagementinformationsystem,facilitatebettermanagement,tocustomerservice.Thisarticlefocusesonthehotelmanagementsystemdesignandimplementation,throughsomeoftherenownedhotelmanagementsystemofreferenceandanalyticalsurveys,combinedwiththecustomer'sneedsandissues,asreflectedinfurtherdetailthedesignofthesystemandneedsanalysis,usetechniquesandWindows2000ServerasadevelopmentplatformthatusestheSQLServer2000dothebackgrounddatabasedevelopment.Thesysteminterfaceisgood,simpleoperation,throughthesystemoverview,systemanalysis,systemsdesign,databasedesign,systemimplementationofthesections,adetaileddescriptionofthesystemdevelopmentprocess,andtheentiredevelopmentprocessaresummarized,enablesavarietyofinformationquery,update,andsoon.目錄摘要 IAbstract II第一章緒論 11.1選題背景及意義 11.2目的 11.3相關(guān)理論基礎(chǔ) 11.3.1ASP.NET與VisualStudio2000 11.3.2SQL與SQLSever2000 31.3.3C#技術(shù) 41.4本章小結(jié) 4第2章可行性研究 52.1經(jīng)濟可行性 52.2技術(shù)可行性 52.3運行可行性 52.4時間可行性 52.5法律可行性 52.6業(yè)務(wù)流程圖 62.7本章小結(jié) 6第3章需求分析 73.1系統(tǒng)需求分析 73.1.1需求分析的任務(wù) 73.1.2需求分析的原則 93.1.3分析系統(tǒng)數(shù)據(jù)流圖 113.1.4數(shù)據(jù)字典 123.1.5需求分析的方法 143.2功能需求 143.3本章小結(jié) 15第4章總體設(shè)計 164.1系統(tǒng)功能設(shè)計 164.2功能模塊圖 164.3處理流程設(shè)計 174.3.1數(shù)據(jù)增加流程 174.3.2數(shù)據(jù)修改流程 184.4數(shù)據(jù)庫詳細設(shè)計 194.5本章小結(jié) 22第5章詳細設(shè)計 235.1首頁 235.2系統(tǒng)首頁 235.3客房信息管理 245.4前臺接待信息管理 245.5收銀信息管理 255.6查詢管理模塊 255.7本章小結(jié) 26第6章系統(tǒng)調(diào)試與測試 276.1程序調(diào)試 276.2程序的測試 276.2.1測試的重要性及目的 276.2.2測試的步驟 286.2.3測試的主要內(nèi)容 29結(jié)論 30致謝 32參考文獻 33附錄1譯文..…………….34附錄2英文參考資料………...………….37第1章緒論1.1選題背景及意義1.2目的1.3相關(guān)理論基礎(chǔ)1.3.1ASP.NET與VisualStudio20001.3.2SQL與SQLSever20001.3.3C#技術(shù)1.4本章小結(jié)第2章可行性研究2.1經(jīng)濟可行性2.2技術(shù)可行性2.3運行可行性2.4時間可行性2.5法律可行性2.6業(yè)務(wù)流程圖圖2-1酒店管理系統(tǒng)業(yè)務(wù)流程圖2.7本章小結(jié)第3章需求分析3.1系統(tǒng)需求分析3.1.1需求分析的任務(wù)3.1.2需求分析的原則3.1.3分析系統(tǒng)數(shù)據(jù)流圖圖3-1系統(tǒng)后臺數(shù)據(jù)流圖3.1.4數(shù)據(jù)字典表3-1數(shù)據(jù)項定義編號名稱別名類型長度I01-01admin_id管理員IDint4I01-02admin_name管理員賬號varchar50I01-03admin_pwd管理員密碼varchar50I01-04users_id員工IDint4I01-05users_name員工賬號varchar50I01-06users_pwd員工密碼varchar50I01-07roomType_id房間類型IDint4I01-08roomType_name房間類型名稱varchar50I01-09user_id客戶IDint4I01-10user_name客戶姓名varchar55I01-11user_age客戶年齡varchar50I01-12user_email電子郵件varchar500I01-13user_tel固定電話varchar50I01-14user_card身份證varchar50I01-15user_address地址varchar50I01-16user_sex性別varchar50I01-17froomId需換房房間int4I01-18troomId所換房間int4I01-19addtime換房時間int8I01-20roomName房間名稱int4I01-21roomMoney房間金額int4I01-22chkis結(jié)賬varchar500I01-23roomMoreMoeny超出付費varchar50I01-24roomDS房間描述varchar500I01-25roosIs房間狀態(tài)varchar55I01-26roomTypeId房間類別編號int42．數(shù)據(jù)流定義數(shù)據(jù)流編號：D1-01數(shù)據(jù)流名稱：管理員密碼數(shù)據(jù)流來源：F1-01數(shù)據(jù)流去向：P1-01數(shù)據(jù)流組成：I01-01+I01-02+I01-03+I01-04+I01-05+I01-06+I01-07+I01-08數(shù)據(jù)流編號：D1-16數(shù)據(jù)流名稱：員工信息數(shù)據(jù)流來源：P1-07數(shù)據(jù)流去向：F1-02數(shù)據(jù)流組成：I01-09+I01-10+I01-11+I01-12+I01-13+I01-14+I01-15+I01-24+I01-25+I01-26+I01-27+I01-28+I01-29+I01-30數(shù)據(jù)流編號：D1-04數(shù)據(jù)流名稱：換房信息數(shù)據(jù)流來源：F1-02數(shù)據(jù)流去向：P1-02數(shù)據(jù)流組成：I01-31+I01-32+I01-33+I01-34數(shù)據(jù)流編號：D1-11數(shù)據(jù)流名稱：入住信息數(shù)據(jù)流來源：F1-03數(shù)據(jù)流去向：P1-03數(shù)據(jù)流組成：I01-47+I01-48+I01-78+I01-01+I01-58+I01-08數(shù)據(jù)流編號：D1-14數(shù)據(jù)流名稱：客人信息數(shù)據(jù)流來源：P1-04數(shù)據(jù)流去向：F1-04數(shù)據(jù)流組成：I01-09+I01-42+I01-43+I01-44數(shù)據(jù)流編號：D1-28數(shù)據(jù)流名稱：房間預訂數(shù)據(jù)流來源：F1-09數(shù)據(jù)流去向：P1-08數(shù)據(jù)流組成：I01-01+I01-39+I01-40+I01-41數(shù)據(jù)流編號：D1-07D-12數(shù)據(jù)流名稱：結(jié)賬退房數(shù)據(jù)流來源：P1-05數(shù)據(jù)流去向：F1-05數(shù)據(jù)流組成：I01-01+I01-09+I01-35+I01-36+I01-373.1.5需求分析的方法3.2功能需求3.3本章小結(jié)第4章總體設(shè)計4.1系統(tǒng)功能設(shè)計4.2功能模塊圖圖4-1功能模塊圖4.3處理流程設(shè)計4.3.1數(shù)據(jù)增加流程圖4-2數(shù)據(jù)增加流程圖4.3.2數(shù)據(jù)修改流程圖4-3數(shù)據(jù)修改流程圖4.4數(shù)據(jù)庫詳細設(shè)計圖4-4員工操作E-R圖表4-5管理員信息表序號列名字段說明數(shù)據(jù)類型長度1id編號IDint42name管理員賬號Varchar553pwd管理員密碼Varchar50表4-6用戶信息表序號列名字段說明數(shù)據(jù)類型長度1id編號IDint42name用戶賬號Varchar503pwd用戶密碼Varchar50表4-7房間類型信息表序號列名字段說明數(shù)據(jù)類型長度1id編號IDint42name名稱Varchar50表4-8客戶信息表序號列名字段說明數(shù)據(jù)類型長度1id編號int42UserName姓名Varchar553UserEmal電子郵件Varchar504UserTel固定電話Varchar505UserMobile手機號碼Varchar506UserCard身份證Varchar507UserSex性別Varchar108UserAddress地址Varchar50表4-9換房記錄信息表序號列名字段說明數(shù)據(jù)類型長度1id編號int42FRoomId需換房房間Varchar503TRoomId換房房間Varchar504UserName換房客戶Varchar505addtime換房時間Varchar500表4-10房間入住信息表序號列名字段說明數(shù)據(jù)類型長度1id編號int42RoomName房間名稱Varchar553RoomId房間編號Varchar504RoomMoney金額Varchar505UserId客人編號Varchar506Addtime入住時間Varchar87Chkis結(jié)賬標志Varchar10表4-11房間預訂信息表序號列名字段說明數(shù)據(jù)類型長度1id編號int42RoomName房間名稱Varchar553RoomId房間編號Varchar504RoomMoney金額Varchar505UserId客人編號Varchar506Addtime入住時間Varchar87Chkis結(jié)賬標志Varchar10表4-12房間信息表序號列名字段說明數(shù)據(jù)類型長度1id編號int42RoomName房間名稱Varchar553RoomTypeId類別編號int44RoomTypeName類別名稱Varchar505RommMoeny房間金額Varchar506RoomMoreMoeny超出付費Varchar507RoomDS房間描述Varchar108RoosIs房間狀態(tài)Varchar504.5本章小結(jié)第5章詳細設(shè)計5.1首頁圖5-1登陸頁面5.2系統(tǒng)首頁圖5-2后臺登陸記錄5.3客房信息管理圖5-3客房信息管理圖5.4前臺接待信息管理圖5-4前臺信息管理圖5.5收銀信息管理收銀信息管理圖如圖5-5所示。圖5-5收銀信息管理圖5.6查詢管理模塊查詢管理模塊包括3個功能模塊分別是：換房記錄查詢，房間信息查詢，房間銷售信息查詢。換房記錄查詢?nèi)鐖D5-6所示。圖5-6換房記錄查詢房間信息查詢?nèi)鐖D5-7所示。圖5-7房間信息查詢房間銷售信息查詢?nèi)鐖D5-8所示。圖5-8房間銷售信息查詢5.7本章小結(jié)本章所述是對界面的詳細設(shè)計，以及各個模塊當中的主要代碼，包括房間信息查詢，客房信息管理，收銀信息管理等模塊。以及該模塊如何實現(xiàn)功能。第6章系統(tǒng)調(diào)試與測試6.1程序調(diào)試6.2程序的測試6.2.1測試的重要性及目的6.2.2測試的步驟6.2.3測試的主要內(nèi)容結(jié)論致謝參考文獻SimonBrown.SamDalton,DanJepp.ASP.NET.ASP.NET.ASP.NETASP.NETC.J.Date.AnintroductiontoDatabaseSystem(SeventhEdition)附錄1譯文數(shù)據(jù)設(shè)計附錄2英文參考資料DataDesignDATATYPESANDVALUESETSAnyonewhohaseverprogrammedacomputerisaccustomedtothefactthatyouusuallyhavetotellthecomputerwhethertheinformationstoredinaparticularlocationisaninteger,arealnumber,acharacterstring,aBooleanva1ue,orwhatever.Mostcomputershaveoneelectroniccircuitforaddingtwointegersandanotherforaddingtworealnumbers,and,ofcourse,additiondoesnotmakeanysenseatall,ingeneral,forcharacterstrings.Becausethepatternofbitsinatstoragelocationcanusual1ybeinterpretedasanyofthese,thecomputermustbetoldwhatisintended.Thisspecificationisknownasthe"type"ofthedata.Identifyingadataobjectasbeingofaparticulartypehastheeffectofdefininganinternalrepresentationfortheobject.Italsospecifieswhichoperationsmaybeperformedonthatobjectandtheireffects.Forexample,theinternalrepresentationofanintegerinmostmodemmainframecomputersisastringof32bitsin2'scomplementformat.Theexternalrepresentationisacharacterstringinwhichonlythedigits0to9andtheminussignmayappear.Suitableinterpretationsofallthestandardarithmeticandlogicaloperationsarealsoimpliedwhenadataobjectisdeclaredtobeoftypeinteger.Itisalsotrue(butperhapslessobvious)thatdeclaringadataobjecttobeanintegerdefinesacollatingsystemforoccurrencesofthatobject.Thatis,itspecifieshowtherelativelycomplexoperation,sort,shouldoperate.Specificalgorithmsforconvertingbetweeninterna1andexternalrepresentationsarealsoimplied.KEYSAllattributesdescribesomeaspectofanentity.Someattributesperformtheadditionalroleofdistinguishingoneparticularentityoccurrencefromallothersofthesametype.Forexample,ifcareistakennottoassignanyemployeenumbertomorethanoneperson,thenknowinganindividual'semployeenumbershouldbesufficienttolocatealloftheotherattributevaluesforthatindividual.

Anattributethatcanbeguaranteedtohaveauniquevalueforeachentityiscalledakey.Sometimestheremaybemorethanoneattributeofanentitythatuniquelyidentifieseachoccurrence.Forexample,ifthepersonnelrecordsincludeSocialSecurityNumbers(andifitisfeltthatthecontrolsonissuingduplicateSocialSecurityNumbersareadequate),theneitherEmployeeNumberorSocialSecurityNumbercouldbeusedasthekeyforidentifyingemployees.KeysarefundamentaltovirtuallyallmethodsofPhysicallymanagingdataincomputersystems.Whenthereismorethanonepossiblekey,thealternativesarereferredtoascandidatekeys.Normally,oneofthesewillbeselectastheprimarykeyandusedtodeterminewheretherecordwillbestored.Othercandidatekeysthatmaybeusedtofacilitateretrievalarecalledsecondarykeys.DATABASESCHEMAThisisadescriptionofthedatawhichisstoredinthedatabaseandspecifieswhatdataelementsarestoreandwhataccesspathsareprovidedbetweentheseelements.Thedatabaseschemaalsocontainsspecificationsofprivacyaswellasintegrityconstraints.Itissomewhatsimilartotheconceptualschema,butisadescriptionofdataratherthanofreality.Someaspectsofrealitywhicharedescribedbydatainthedatabaseschema.Note,however,thatthedatabaseschemadoesnotspecifyhowthedataisactuallystoredorhowaccesspathsareprovided.(Ideallyitshouldnotrefertofiles,records,setsorthelike.)Itis,therefore,animplementationindependentdescriptionandforthisreasonissometimesreferredtoaslogicalschema.Thatpartofthedatabaseschemawhichisofinteresttoaparticularend-userorgroupofend–usersiscalledadatabasesub-schema.Ideally,asub-schemashouldbespecifiedusinganotationwhichismostappropriatefortheusetowhichitisbeingput.Databasesub-schemashaveseveraluse:(1)theycanbereferredtobyapplicationprogrammerstoseewhataccesspathsareavailableinthatpartofthedatabaseinwhichtheyareinterested(2)similarly,theycanbereferredtobytheend-userswhentheyareusingareportprogramgeneratororformulatingqueriesetc.usingaquerylanguageprovided.(3)theycanbeusedtodividethedatabaseintounitsforthespecificationofprivacyconstrains.Forexample,asub-schemacouldbedefinedforwhichallusershavereadaccessbutonlyonespecifieduserhaswrite(update)access.PHYSICALSCHEMAThephysicalschemaisadescriptionofthephysicalstructureofthedatabase.If,forexample,conventionalindexed-sequentialfilesareusedtostorethedatabase,thenthiswillbestatedinthephysicalschema.Itwillalsocontaindetailsofrecordformats,blockingfactorsetc.Thephysicalschemaisconstructedasanessentialpartofthedesignprocess.However,itmayalsobeusedasanintegeralpartofheoperationaldatabasesystemasdiscussedbelow.Thephysicalschemaissometimescalledtheinternalschema.PHYSICALSTORAGESTRUCTUREThestructureinwhichthedatabaseactuallyresidesistermedthephysicalstoragestructure.Ittypicallyconsistsofdiscfiles,tapes,mainstore,indicesandprogramstomanipulatethesecomponents.BACK-UPANDRECOVERYSYSTEMTheback-upandrecoverysystemisthemodulewhichrebuildsthedatabaseaftercorruptionduetohardwareorsoftwarefailure.UnderstandingtheApplicationTasksOneoftheoften-neglectedstepsonbuildingsoftwareisreallyunderstandingtheenduser’sjob-thethatcomputerautomationisintendedtosupport.Occasionally,thisisbecausetheapplicationitselfisquitespecialized;moreoften,itisbecausetheapproachtodesigntendstobedata-oriented.Frequently,thesearethemajorquestionaskedintheanalysis:(1)Whatdatashouldbecaptured(2)HowshouldthedatabeprocessedThesequestionexpandintoaseriesofsubquestion,andincludeissuessuchasinputforms,Codes,screenlayouts,computations,postings,corrections,audittrails,retention,storagevolumes,processingcycles,reportformatting,distribution,andmaintenance.thereareallvitallyimportantareas.Onedifficulty,however,isthattheyallfocussolelyondata.Peopleusedata,buttheydotasks.Onemightarguethatwhilethismaybetrueofprofessionalworkers.Key-entryclerksreallyonlytransferdatafromaninputformtoakeyboard;theirtasksareverydata-oriented.Thisisafairportrayaloftheirjobstoday,butisthisaconsequenceoftherealjobthatneedtogetdone,orisitasymptomofthecomputerapplication?Usinghumansasinputdevices,particularlyfordatathatisvoluminous,consistentinformat(asonforms),andinalimitedrangeofvariability,isanexpensiveandantiquated,nottomentiondehumanizing,methodofcapturingdata.Thismaysoundlikesomuchphilosophy,butithaspracticalimportinthewayapplicationdesignisdone.Peopleusedata,buttheydotasks.Andtheydon’tdotasksthroughocompletiononeatatime.Theydosev