毕业论文-基于SQL Server的酒店管理信息系统

摘要关键字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相关理论基础 11.3.1ASP.NET与VisualStudio2000 11.3.2SQL与SQLSever2000 31.3.3C#技术 41.4本章小结 4第2章可行性研究 52.1经济可行性 52.2技术可行性 52.3运行可行性 52.4时间可行性 52.5法律可行性 52.6业务流程图 62.7本章小结 6第3章需求分析 73.1系统需求分析 73.1.1需求分析的任务 73.1.2需求分析的原则 93.1.3分析系统数据流图 113.1.4数据字典 123.1.5需求分析的方法 143.2功能需求 143.3本章小结 15第4章总体设计 164.1系统功能设计 164.2功能模块图 164.3处理流程设计 174.3.1数据增加流程 174.3.2数据修改流程 184.4数据库详细设计 194.5本章小结 22第5章详细设计 235.1首页 235.2系统首页 235.3客房信息管理 245.4前台接待信息管理 245.5收银信息管理 255.6查询管理模块 255.7本章小结 26第6章系统调试与测试 276.1程序调试 276.2程序的测试 276.2.1测试的重要性及目的 276.2.2测试的步骤 286.2.3测试的主要内容 29结论 30致谢 32参考文献 33附录1译文..…………….34附录2英文参考资料………...………….37第1章绪论1.1选题背景及意义1.2目的1.3相关理论基础1.3.1ASP.NET与VisualStudio20001.3.2SQL与SQLSever20001.3.3C#技术1.4本章小结第2章可行性研究2.1经济可行性2.2技术可行性2.3运行可行性2.4时间可行性2.5法律可行性2.6业务流程图图2-1酒店管理系统业务流程图2.7本章小结第3章需求分析3.1系统需求分析3.1.1需求分析的任务3.1.2需求分析的原则3.1.3分析系统数据流图图3-1系统后台数据流图3.1.4数据字典表3-1数据项定义编号名称别名类型长度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结账varchar500I01-23roomMoreMoeny超出付费varchar50I01-24roomDS房间描述varchar500I01-25roosIs房间状态varchar55I01-26roomTypeId房间类别编号int42．数据流定义数据流编号：D1-01数据流名称：管理员密码数据流来源：F1-01数据流去向：P1-01数据流组成：I01-01+I01-02+I01-03+I01-04+I01-05+I01-06+I01-07+I01-08数据流编号：D1-16数据流名称：员工信息数据流来源：P1-07数据流去向：F1-02数据流组成：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数据流编号：D1-04数据流名称：换房信息数据流来源：F1-02数据流去向：P1-02数据流组成：I01-31+I01-32+I01-33+I01-34数据流编号：D1-11数据流名称：入住信息数据流来源：F1-03数据流去向：P1-03数据流组成：I01-47+I01-48+I01-78+I01-01+I01-58+I01-08数据流编号：D1-14数据流名称：客人信息数据流来源：P1-04数据流去向：F1-04数据流组成：I01-09+I01-42+I01-43+I01-44数据流编号：D1-28数据流名称：房间预订数据流来源：F1-09数据流去向：P1-08数据流组成：I01-01+I01-39+I01-40+I01-41数据流编号：D1-07D-12数据流名称：结账退房数据流来源：P1-05数据流去向：F1-05数据流组成：I01-01+I01-09+I01-35+I01-36+I01-373.1.5需求分析的方法3.2功能需求3.3本章小结第4章总体设计4.1系统功能设计4.2功能模块图图4-1功能模块图4.3处理流程设计4.3.1数据增加流程图4-2数据增加流程图4.3.2数据修改流程图4-3数据修改流程图4.4数据库详细设计图4-4员工操作E-R图表4-5管理员信息表序号列名字段说明数据类型长度1id编号IDint42name管理员账号Varchar553pwd管理员密码Varchar50表4-6用户信息表序号列名字段说明数据类型长度1id编号IDint42name用户账号Varchar503pwd用户密码Varchar50表4-7房间类型信息表序号列名字段说明数据类型长度1id编号IDint42name名称Varchar50表4-8客户信息表序号列名字段说明数据类型长度1id编号int42UserName姓名Varchar553UserEmal电子邮件Varchar504UserTel固定电话Varchar505UserMobile手机号码Varchar506UserCard身份证Varchar507UserSex性别Varchar108UserAddress地址Varchar50表4-9换房记录信息表序号列名字段说明数据类型长度1id编号int42FRoomId需换房房间Varchar503TRoomId换房房间Varchar504UserName换房客户Varchar505addtime换房时间Varchar500表4-10房间入住信息表序号列名字段说明数据类型长度1id编号int42RoomName房间名称Varchar553RoomId房间编号Varchar504RoomMoney金额Varchar505UserId客人编号Varchar506Addtime入住时间Varchar87Chkis结账标志Varchar10表4-11房间预订信息表序号列名字段说明数据类型长度1id编号int42RoomName房间名称Varchar553RoomId房间编号Varchar504RoomMoney金额Varchar505UserId客人编号Varchar506Addtime入住时间Varchar87Chkis结账标志Varchar10表4-12房间信息表序号列名字段说明数据类型长度1id编号int42RoomName房间名称Varchar553RoomTypeId类别编号int44RoomTypeName类别名称Varchar505RommMoeny房间金额Varchar506RoomMoreMoeny超出付费Varchar507RoomDS房间描述Varchar108RoosIs房间状态Varchar504.5本章小结第5章详细设计5.1首页图5-1登陆页面5.2系统首页图5-2后台登陆记录5.3客房信息管理图5-3客房信息管理图5.4前台接待信息管理图5-4前台信息管理图5.5收银信息管理收银信息管理图如图5-5所示。图5-5收银信息管理图5.6查询管理模块查询管理模块包括3个功能模块分别是：换房记录查询，房间信息查询，房间销售信息查询。换房记录查询如图5-6所示。图5-6换房记录查询房间信息查询如图5-7所示。图5-7房间信息查询房间销售信息查询如图5-8所示。图5-8房间销售信息查询5.7本章小结本章所述是对界面的详细设计，以及各个模块当中的主要代码，包括房间信息查询，客房信息管理，收银信息管理等模块。以及该模块如何实现功能。第6章系统调试与测试6.1程序调试6.2程序的测试6.2.1测试的重要性及目的6.2.2测试的步骤6.2.3测试的主要内容结论致谢参考文献SimonBrown.SamDalton,DanJepp.ASP.NET.ASP.NET.ASP.NETASP.NETC.J.Date.AnintroductiontoDatabaseSystem(SeventhEdition)附录1译文数据设计附录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