【正文】 evel. Principle is to ensure that operators will not affect the speed of efficiency. In the process of developing “Chain Hotel management system”, expandability should be taken into consideration. For example, with the change in the way of management system, users’ demand for inquiry will 17 also be continuously updated and pleted. All of these request the system to provide sufficient ways in adjusting and expanding the function [4]. This should be realized through the openness of the system. That is, system should be open as well as be able to increase and decrease system module simply and deploy system hardware on the premise of plying with certain standard. Through fixing and replacing the software, the promotion and update of system is pleted. The system assures its easiness in application and maintenance. The Users “Chain Hotel management system” directly deals with are not puter professionals, which calls for the system to provide favorable customer interface and friendly humanputer interaction interface. To realize this, it requires the system to use technical terms that are familiar to users and interface of Chinese information as much as possible. To aim at possible handling problems users may e across, sufficient online help should be provided, shortening the process of the users’ familiarization with the system [5]. Fig. 7. Scheduled activity diagram a) Login screen: When startup program, the login screen will be shown, it is used for user login. b) Tray icon: the program starts only in the Windows tray icon to display a program. c) The main interface: the major chain hotel management system user interface. d) Booking management interface, hotel management interface, payment management interface, customer management interface: Click to access all the interfaces were. 18 5 Operational Requirements User Interface Spreading between different interfaces can also be expressed in UML models, but in the UML specification and graphical representation do not have specific diagram to express, and can be represented by state diagram. References System requirements analysis using use case diagrams, sequence diagrams, interaction diagrams, activity diagrams to describe it. Through the use case diagram and activity diagram can neatly analyze business requirement, so that users and developers can quickly grasp the main features of the system for system development. Reunification of UML modeling language is a mon language for model。在用例圖表和活動(dòng)圖表中能分析商務(wù)需求，這樣用戶和開發(fā)者就能快速地掌握系統(tǒng)開發(fā)中的系統(tǒng)主要需求。在開發(fā)酒店管理系統(tǒng)的過程中，擴(kuò)展性應(yīng)該被考慮在內(nèi)。因此，活動(dòng)圖表是用來給用例模型建立工作控制流，詳細(xì)闡述用例模型。從預(yù)訂中心的工作來判斷，計(jì)算機(jī)的普及的確解決了傳統(tǒng)電話預(yù)定的問題，即員工在接電話時(shí)被迫親自寫訂單，接著再通過各種方法把信息傳到前臺(tái)。所有的這些缺陷造成了所設(shè)計(jì)的系統(tǒng)缺少一個(gè)清楚的架構(gòu)，而且還降低了系統(tǒng)的靈活性和擴(kuò)展性。它使得系統(tǒng)分析很容易被復(fù)雜的系統(tǒng)功能弄得混亂，而且還缺少對(duì)整體框架的認(rèn)識(shí)，即系統(tǒng)和需求視圖的邏輯結(jié)構(gòu)。 3 功能行為需求 商務(wù)功能需求模型 通過連鎖酒店的調(diào)查過程，完成了用例模型。 活動(dòng)圖表提供了用例圖表之后的系統(tǒng)描述，能解釋更多關(guān)于系統(tǒng)的執(zhí)行過程，以及在各種情況下如何改變執(zhí)行的方向。 原則是保證使用者不會(huì)影響效率。 9 參考文獻(xiàn) 系統(tǒng)需求分析使用用例圖表、序列圖表、交互圖表和活動(dòng)圖表來描述。 also it provide systems analysis provides a mon symbol system that can meet a number of software。 b） 托盤圖標(biāo)：程序只從 Windows托盤圖標(biāo)啟動(dòng)來顯示程序。在系統(tǒng)設(shè)計(jì)和開發(fā)階段，必須充分考慮系統(tǒng)現(xiàn)在和將來將要承受的工作量。 操作狀態(tài)指示可執(zhí)行的和不可分割的動(dòng)作執(zhí)行。 （ 4） 系統(tǒng)管理員：維護(hù)系統(tǒng)數(shù)據(jù)，添加、刪除或更新顧客房間、連鎖酒店的會(huì) 員的所有信息，修改會(huì)員的優(yōu)惠信息。因此，這些結(jié)果為系統(tǒng)的后續(xù)開發(fā)和實(shí)施提供有效的基礎(chǔ)。 面向?qū)ο蟮慕ＵZ言，統(tǒng)一建模語言（ UML），被廣泛認(rèn) 可發(fā)明在 70 年代中期。預(yù)訂管理的用例圖如圖 2